Updating

Updating

Updates are manual. Changing GitHub code does not update your server.

1. Back up the existing notebook and preserve its deployment files before changing versions. When making a raw filesystem copy, stop QSObook and copy the complete data directory, including SQLite journals.
2. Download the new release's Compose files and checksum manifest from GitHub Releases. Verify checksums.
3. Preserve the same .env, project name and named data volume. Pull the new digest-pinned image, then recreate the service with Compose.
4. Open Preferences → About, check the installed version, then verify stations, Notebook and QSO mode.

Never use down -v, delete qsobook_data or prune volumes to update. Beta 5 and stable v0.1.0 both use schema 7; updating between them requires no database migration. Beta 4 cannot open that schema; rolling back requires a separately preserved pre-upgrade backup, not merely selecting an older image.

The :stable and :latest channels follow stable releases; :beta remains a separate prerelease channel. Pinned version/digest downloads make an intentional update reproducible. There is no automatic update agent or mandatory cloud service.

See the exact update and backup commands.

v0.2.0 adds schema 8 and optional RadioID, off after migration. Previous v0.1.0 uses schema 7. Opening an older notebook with v0.2.0 upgrades it; returning to v0.1.0 requires the separately preserved schema-7 backup. Read the source-build guide and compatibility table before switching distributions. Installing v0.2.0 requires downloading its new release files; pulling an old digest-pinned Compose file keeps its original version.