Upgrading
Back up, pull the new version, rebuild, and roll back if something goes wrong. Migrations run automatically at start-up.
Before you start: read the release notes for the version you are moving to (see the changelog), and have a working backup process.
-
Back up first:
docker compose exec glideworth node dist/cli/admin.js backup --out /data/backups/pre-upgrade.db -
Update and rebuild:
git pull docker compose up -d --build docker compose logs --tail 50 glideworthDatabase migrations are applied automatically at start-up. Check that
docker compose psshows “healthy”. -
If it goes wrong, check out the previous version (
git checkout <previous tag>) and rebuild. If the database was changed in a way the old version cannot read, restorepre-upgrade.db.
Use release tags rather than the main branch for production. If you have skipped several versions, upgrade one minor version
at a time and read the notes for each. If you run a pre-built image, replace the build step with docker compose pull and
pin the version tag in your override file.
What this does not do
It does not downgrade the database. Going back across a schema change means restoring a backup taken before the upgrade.
Last checked against the code on .