Upgrading

Upgrade

Statup backs up the database before an upgrade changes it, unless Back up before each upgrade is turned off in Settings › Backups. The file, statup-before-<version>-<date>.db, goes to BACKUP_DIR, and the three latest are kept. If that backup cannot be written, the upgrade goes on and the server logs the failure. For a copy that does not sit on the same disk, see Keep a copy elsewhere.

Then:

docker compose pull
docker compose up -d

The database is migrated when the new version starts: the migrations are compiled into the binary. A database migrated by a newer version is refused by an older one, so going back means restoring the backup made before the upgrade.

Administrators see the running version in Settings, and the newer one once it is published, unless UPDATE_CHECK is false.

Stay on a version

latest follows each new version. To upgrade only when you choose, replace latest with a version number under image: in docker-compose.yml:

image: ghcr.io/karl-cta/statup:0.12.0

Every version and what it changed are in the changelog. Statup is before its 1.0: expect changes between versions, and keep a copy of the backups away from the server.

Upgrade on Linux

Run the install command again: the script updates Statup and keeps its settings. See Install on Linux.

Upgrade on Windows Server

Run the install script again: it updates the service and keeps its settings. See Install on Windows Server.