Production Runtime
Runtime startup/migration mechanics are documented in Bootstrap & Generated Artifacts.
Operational guidance
- Sequence deployments so only one new release performs first startup against the target database.
- Monitor startup logs and fail fast if migration application does not complete.
- Keep rollback expectations explicit: if a deployment fails after schema changes, verify old runtime compatibility with the migrated schema before rollback.
Failure mode
If migration application fails, Zeptoz returns a DB_MIGRATION error and startup does not continue.
Check:
- database connectivity and credentials
- schema compatibility between existing DB state and bundled migrations
- database permissions needed to apply schema changes
- startup logs for the underlying migration error details
Pre-deploy verification checklist
- Take a backup or snapshot of production data.
- Validate startup in a staging/test environment with production-like schema state.
- Confirm expected migrations are present in the release build.
- Perform post-start smoke checks (for example
/healthand/openapi.json).