Skip to content

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.

  1. Read the changelog for the versions you’re skipping.
  2. Make a backup. Migrations only go forward, so the backup is your way back.

Set the new version in .env, then pull and restart.

Terminal window
DAY_PLANNER_VERSION=1.1.0
Terminal window
docker compose pull app
docker compose up -d app
docker compose logs -f app

The logs show Applying migration … for any database changes, then Ready. If you use latest instead of a pinned version, skip the .env change.

Because migrations aren’t reversed, rolling back is a restore:

  1. Set DAY_PLANNER_VERSION back to the old version.
  2. Restore the backup you made before upgrading.
  3. docker compose up -d app.

Anything created between the upgrade and the rollback is lost, so roll back quickly or not at all.