Upgrading and Rollback

Upgrading and rollback

Back up the config directory before changing image versions. It contains the database and application state needed for a restore.

Upgrade

From the directory containing compose.yaml:

docker compose pull
docker compose up -d
docker compose ps

If the deployment uses a pinned tag, update it in compose.yaml before pulling. Open Pinchflat-ngx and review Settings > Diagnostics after the container becomes healthy.

Do not interrupt the container while startup migrations are running.

PostgreSQL deployments must keep the server major version aligned with the image. Current Pinchflat-ngx PostgreSQL images expect PostgreSQL 18. Rolling back the app image does not downgrade the PostgreSQL data directory.

Roll back

Changing the image tag does not reverse database migrations. If an upgrade migrated the database, restore both the previous image and the config backup created immediately before the upgrade.

1. Stop Pinchflat-ngx with docker compose down.
2. Restore the previous config directory as described in Backups and restore.
3. Set the previous image tag in compose.yaml.
4. Run docker compose up -d, then check container health and logs.

Downloaded media normally does not need to be rolled back, but its paths must remain consistent with the restored database.