Updating
Install the newest release your licence covers with one command on Linux or macOS, pull the new image on Docker, and what the command does step by step.
chronoslice update downloads the newest release your licence covers, checks it, backs up your database, swaps the program and restarts the service. It works on Linux and on macOS. In Docker it only checks, and you update by pulling the new image. This page shows how to find out an update is available, how to run it, and how to go back.
See that an update is available
- In the app. When the store has a newer release for your key, owners and admins see a note in Settings, then Licence:
ChronoSlice 0.2.0 is available, with its release date. What's new opens the release notes, and the card shows the command to run,sudo chronoslice update, with a Copy button. The Licence link in the settings list also gains· update. The server asks the store once a day, and Check now asks straight away. - At a shell.
sudo chronoslice update --checksays whether there's a newer release and prints its notes. It changes nothing.
Run the update
Run it on the server with sudo. It must run as a user that can write to the folder holding the program, which is root for /usr/local/bin, and it reads the service's settings from /etc/chronoslice/env.
sudo chronoslice update
It prints the version and its notes, then asks Install ChronoSlice 0.2.0 over /usr/local/bin/chronoslice? [y/N]. Answer y. To skip the question, for a script, add --yes:
sudo chronoslice update --yes
The server restarts for a few seconds. The web app reconnects by itself, and the Mac app keeps working offline and syncs when the server is back.
What it does, step by step
- Asks the store for the newest release your key may have, and refreshes the signed statement about your key.
- Compares versions. If you already run the newest release, it says
ChronoSlice 0.1.0 is the newest release this licence covers.and stops. If your updates have ended, it also says when, and where to renew. - Prints what's new: the version, its release date and the release notes. With
--check, it stops here. - Picks the build for this machine:
chronoslice-<version>-linux-x86_64.tar.gzorchronoslice-<version>-linux-arm64.tar.gzon Linux, andchronoslice-<version>-macos-universal.tar.gzon a Mac. On a system it has no build for, it tells you to download from your account instead. - Checks it can write to the folder that holds the program, before downloading anything.
- Asks you to confirm, unless you gave
--yes. With no terminal to ask on and no--yes, it refuses. - Downloads the archive next to the program and checks its SHA-256 against the store's. If they differ, nothing is installed. It takes the new program out of the archive and runs it with
--versionto make sure it's the right release. - Backs up the database to
backup-pre-<version>.db, in the same folder as the database. If that name is taken, it adds-2,-3and so on. - Swaps the program. The old one is kept beside it as
chronoslice.previous. - Restarts the service, if it's running. On Linux that's
systemctl restart chronoslice. On a Mac it'slaunchctl kickstart -k system/dev.chronoslice.server. The new release brings the database up to date as it starts.
If anything fails before step 9, your program and database are untouched, and the temporary files are removed.
Because you run it as root, the backup file and the database's -wal and -shm files are given the owner of the database file, so the service can still write to them.
Options
| Option | What it does |
|---|---|
--check |
Only say whether there's a newer release. |
--yes, -y |
Install without asking. |
--no-restart |
Don't restart the service afterwards. Restart it yourself when you're ready. |
--service <name> |
The service to restart: a systemd service on Linux, or a launchd label on a Mac. The default is chronoslice on Linux and dev.chronoslice.server on a Mac. |
--db <url> |
The database, if the settings file doesn't name it. |
If you don't run ChronoSlice under systemd or launchd, use --no-restart and restart it the way you normally do. sudo chronoslice update --no-restart prints Restart ChronoSlice to run the new release (it migrates the database as it starts).
On a Mac
The command is the same, and it's sudo chronoslice update for the program at /usr/local/bin/chronoslice. It finds the daemon from Install on macOS, dev.chronoslice.server, and restarts it with launchctl. It also finds a launchd job of the same name that runs under your own login, if you set ChronoSlice up that way instead. If you named the daemon something else, pass --service <label>. The old program is kept as /usr/local/bin/chronoslice.previous, and the database copy is backup-pre-<version>.db beside the database, in /usr/local/var/chronoslice.
In Docker
chronoslice update doesn't replace anything inside a container. Run in the Docker image, it says whether a newer release is out and prints its notes, then reminds you to pull the new image. To update, pull it and recreate the container:
docker compose pull && docker compose up -d
The new release brings the database up to date as it starts. It makes no backup-pre-<version>.db copy for you, so take one first with docker compose exec chronoslice chronoslice backup /data/before-update.db, and use a new name each time. If you pinned a version in compose.yaml, change the tag to the new version first. To go back, put the old tag in compose.yaml and restore the database copy, as in Backups and restoring. See Run with Docker.
After the update
Check the version and the log. On Linux:
chronoslice --version
journalctl -u chronoslice -n 20
On a Mac, check the version and the end of the log:
chronoslice --version
tail -n 20 /usr/local/var/log/chronoslice.log
Settings and data stay as they were. The backups pile up, one for each update, so delete old ones when you're happy with the new release.
If something goes wrong
On Linux, go back to the previous program and your database copy:
sudo systemctl stop chronoslice
sudo mv /usr/local/bin/chronoslice.previous /usr/local/bin/chronoslice
sudo mkdir -p /var/lib/chronoslice/aside
sudo mv /var/lib/chronoslice/chronoslice.db-wal /var/lib/chronoslice/chronoslice.db-shm /var/lib/chronoslice/aside/ 2>/dev/null
sudo cp /var/lib/chronoslice/backup-pre-0.2.0.db /var/lib/chronoslice/chronoslice.db
sudo chown chronoslice:chronoslice /var/lib/chronoslice/chronoslice.db
sudo systemctl start chronoslice
Use the name of the backup from the release you installed. Restoring the copy goes back to how your data was before the update, so anything you entered since is lost. You need the copy because an older program may refuse to start on a database that a newer release has already changed. The -wal and -shm files belong to the newer database, so they're moved aside before the copy goes in. Backups and restoring has more on restoring.
On a Mac, the steps are the same. Run the file commands as the account that owns /usr/local/var/chronoslice, and use sudo for the program and the daemon:
sudo launchctl bootout system/dev.chronoslice.server
sudo mv /usr/local/bin/chronoslice.previous /usr/local/bin/chronoslice
mkdir -p /usr/local/var/chronoslice/aside
mv /usr/local/var/chronoslice/chronoslice.db-wal /usr/local/var/chronoslice/chronoslice.db-shm /usr/local/var/chronoslice/aside/ 2>/dev/null
cp /usr/local/var/chronoslice/backup-pre-0.2.0.db /usr/local/var/chronoslice/chronoslice.db
sudo launchctl bootstrap system /Library/LaunchDaemons/dev.chronoslice.server.plist
If there's no update to install
No licence key is entered on this server.chronoslice updateneeds a key. See Buying and entering a licence.- It says you're on the newest release but you expect a newer one. Your updates may have ended. The message says so, with the date. See When updates end.
there's no ChronoSlice database at …. Run the command with the service's settings. Usesudo, or pass--db.
Related
Still stuck?
Send us a request: it goes to the people who build ChronoSlice, and the reply comes by email. Include your ChronoSlice version (Settings › Licence shows it) and what you tried.