Upgrades & Rollback
Move to new releases safely, and roll back if something goes wrong.
Upgrades are designed to be boring: pull newer images, recreate the containers, keep the data volumes. Your projects, knowledge bases, and license are preserved across upgrades.
Standard upgrade
- 1Take a fresh backup (see Backup & Restore).
- 2Re-run your install command — it detects the existing install and upgrades it — or pull the latest images and recreate containers with Docker Compose.
- 3Verify with the health check and confirm the new version at /api/version.
Database migrations
Schema migrations run automatically on startup and are designed to be forward-safe. The pre-upgrade backup is your safety net — take it every time.
Rolling back
- 1Stop the application services.
- 2Start the previous image version.
- 3If the newer release migrated the schema, restore the pre-upgrade database backup as well.
Running CrestBid for a team and need zero-downtime upgrades or high-availability patterns? Those are documented for Enterprise deployments — contact sales.