Updates and auto-update
Nothing updates by itself. Admin > System tells you when a release is out, you take a backup, and then one command or one button brings the new version.
1. Back up first, every time
Database migrations run by themselves at startup and are forward-only: an older version cannot use a schema a newer one has changed. So take a backup before every update:
BACKUP_DIR=/path/to/backups ./scripts/backup.sh
A server made with the setup assistant has no scripts/ folder yet. Fetch the scripts of the release you run once; replace X.Y.Z with the version in Admin > System:
base=https://raw.githubusercontent.com/mnema-xyz/talk/vX.Y.Zmkdir -p scripts && cd scriptsfor f in backup.sh backup-common.sh backup-online.sh restore.sh upgrade-postgres.sh health-check.sh; do curl -fsSLO "$base/scripts/$f"; donechmod +x *.sh && cd ..
More in Backups and restore.
2. Which tag you follow
MNEMA_IMAGE in .env decides what an update brings:
| Tag | Follows | Update now button | Command line |
|---|---|---|---|
:X.Y (for example :3.3) | All patch releases of that line | Yes, until the next minor line | docker compose pull && docker compose up -d |
:latest | Every release, breaking ones included | Always | docker compose pull && docker compose up -d |
:X.Y.Z or @sha256:… | Nothing: pinned | No; the System tab shows the steps | Upgrading between versions |
The setup assistant writes a tag for the version it came with. :X.Y is the practical middle ground: a fix release bumps the patch, so :X.Y receives only fixes. GHCR has no :X tag (the Docker Hub mirror mnemaxyz/mnema-talk also carries :X).
3. Update from the command line
For :X.Y and :latest:
cd /path/to/mnema-talkdocker compose pull && docker compose up -d
Compose recreates only the services whose image changed; the downtime is a few seconds. Open tabs show “A new version is available – click here to reload”, and a call in progress reconnects after the reload.
On Synology without SSH: Container Manager > Project > mnema-talk > Action > Stop, then Clean (removes the project's containers and images, not your data) and Build.
The Update now button
Admin > System shows the running version and the newest release with its notes. The server asks GitHub every 30 minutes; UPDATE_CHECK_ENABLED=false turns that off.
The optional updater sidecar adds an Update now button. Before anything is pulled, it resolves the tag to one digest and verifies the image's cosign signature against this project's release workflow and the build provenance of every platform. It refuses an image that is older than the running one, so a moved tag cannot roll the app back. Then it pulls exactly that digest and restarts only the app; everyone is disconnected for about 30 to 60 seconds. It asks for the Owner's password again, runs at most once every 5 minutes and is written to the audit log.
It is off by default. Enable it when the setup assistant asks, or add two lines to .env and start the profile:
COMPOSE_PROFILES=autoupdate
UPDATER_TOKEN=<output of: openssl rand -hex 32>
docker compose up -d
It needs a released image (not a local build) and outbound HTTPS to ghcr.io and Sigstore.
4. Check the result
docker compose pscurl -fsS http://127.0.0.1:8080/api/healthdocker compose logs --since 10m app | grep -E 'migration applied|"level":"(WARN|ERROR)"'
The app should be healthy after about 15–30 seconds. Admin > System shows the new version; then look at Admin > Status for new amber or red items.
For every release you skip, read its entry in the upgrade notes: some need a setting changed before you update. If something goes wrong, see Upgrading between versions.