Skip to main content

Updating and migrating versions

Version status​

Use published release notes and pinned image references to identify the version you are running and the version you intend to deploy.

Before updating​

Create a backup, verify it can be restored, keep .env and encryption keys safe, and record your current image/version before changing anything.

Standard Docker Compose update​

docker compose pull app
docker compose up -d --force-recreate app
docker compose ps

Then inspect logs and test sign-in, core pages, and integrations.

PostgreSQL​

Do not make a major PostgreSQL upgrade by pointing an old data volume at a newer major image. Perform a controlled backup/migration/restore and validate it separately.

Rollback​

Roll back only to a known compatible application image and database state. If schema changes are involved, restore the matching backup rather than assuming a container-image rollback is sufficient.

Validation after updating​

  • Containers are healthy.
  • Admin and Customer Portal work.
  • Authentication works.
  • Scheduled jobs and notifications run.
  • Integrations pass diagnostics.
  • No sensitive errors are present in logs.