Upgrading
Each release is published as a versioned image, ghcr.io/deejpotter/day-planner:{version}. Upgrading means running a newer image; the database is migrated automatically when it starts.
Before you upgrade
Section titled “Before you upgrade”- Read the changelog for the versions you’re skipping.
- Make a backup. Migrations only go forward, so the backup is your way back.
Upgrade with Docker Compose
Section titled “Upgrade with Docker Compose”Set the new version in .env, then pull and restart.
DAY_PLANNER_VERSION=1.1.0docker compose pull appdocker compose up -d appdocker compose logs -f appThe logs show Applying migration … for any database changes, then Ready. If you use latest instead of a pinned version, skip the .env change.
Roll back
Section titled “Roll back”Because migrations aren’t reversed, rolling back is a restore:
- Set
DAY_PLANNER_VERSIONback to the old version. - Restore the backup you made before upgrading.
docker compose up -d app.
Anything created between the upgrade and the rollback is lost, so roll back quickly or not at all.
See also
Section titled “See also”- Migration failed: if the new version won’t start
- Running more than one instance: upgrades with several containers