What to back up
The canonical backup and restore procedure - application PostgreSQL,
BETTER_AUTH_SECRET, BISIBILITY_SECRETS_KEY, Valkey, Temporal persistence,
restore commands, and restore rehearsal - lives on the Self-host page:
Backup and restore.
Upgrade Docker Compose
v0.5.0 is a fresh-install reset with one squashed Prisma baseline. Existing
v0.4.1 and earlier databases do not have a supported upgrade path to v0.5.0,
and the v0.5.0 upgrade.sh refuses before changing Compose or the database.
Keep web and worker on the same version
The web app and Temporal worker share one Prisma schema. For a split deployment,
back up PostgreSQL, deploy the web app so migrations apply, then immediately
deploy the worker from the same release tag. Version skew commonly appears as
“The column … does not exist” errors in worker logs or as failing scheduled
checks while the web app works. For startup and version-skew diagnosis, see
the canonical Troubleshooting runbook. Follow
the canonical upgrade procedure for both services.
Verify and roll back
Readiness checks and rollback procedure live on the canonical Self-host pages.
After an upgrade, validate readiness using the checks on
Self-hosted upgrades. Rolling the application image
back does not reverse Prisma migrations; see
Backup and restore for the restore-and-migrate
rollback path. For managed platforms, use the platform database backup and
rollback features, but keep independent exports for disaster recovery.
Deployment topology is in Self-hosting.