Database
Database migrations have a paved path: migrator
Theseus services now define schema migrations as a forward/backward SQL contract and run them from a migrator hook before each release starts, with validation, a rollback path, and one pass/fail signal. Agreed with Data Engineering; ready to adopt in every new service.
Run database migrations with migrator
Task recipes for migrator: author and validate migrations, build the derived image in CI, run them as a migration hook in your chart, adopt an existing database, roll back, and read the result.
Roll back a deployment
The fastest ways to get production back to the last good version on Runway, in order of speed, and what rollback means on a Cell.
Add database migrations to your service
Take a scaffolded service from schema-at-startup to versioned, reversible migrations run by migrator: author, validate, apply, roll back, package, and run them before each release.