Apply database schema changes for Express · Ample Computer
Apply database schema changes for Express
Apply database schema changes for an Express app on Ample with a release command. The command runs against the injected DATABASE_URL before the new release goes live, and the release fails instead of activating if the migration fails.
What it runs on
Computeverified
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.Postgresverified
Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and noDATABASE_URLis supplied.
You need
- A migration script that reads
process.env.DATABASE_URLand exits non-zero on failure - A PostgreSQL database (supplied or managed)
- An Ample account token with
servers:writeanddatabases:read
Exact tested configuration
buildnpm run build --if-presentinstallnpm installruntimenodesizes1vcpu-1gbstartnpm run starttemplatenode-22
Steps
Write an idempotent migration. Create tables and markers with
IF NOT EXISTSor a migration tool so a re-run is safe.Deploy with the release command. Ample runs the command before activation; a non-zero exit fails the release.
$ ample deploy . --name <app-name> --public --release-command "node migrate.js"
Verify the marker through the app. Serve a route that reads something only the migration creates.
Verify. Fetch the live URL and run the success checks below. On failure read the build log, then the runtime log, fix the cause and deploy again; do not blind-retry.
$ ample logs <deployment_id> --kind build
How it was checked
✓ migration marker is readable · http get/migrated → “migrated=release-ok”
Evidence
November 5, 2026 · canary run
A--release-commandmigration ran before the release went live;/migratedreported the marker the migration created.November 6, 2026 · canary run
Express app withnpm installandnpm run startdeployed on thenode-22template; the public URL served the expected response.
Tested examples
- Release-command migration canary.
node migrate.jscreates a marker table before activation;/migratedreads it.
What it doesn’t cover
- Verified on the
node-22template ats-1vcpu-1gb. - Managed PostgreSQL 16 with pgvector.
- Apps and their managed databases are placed together, in the same region.
- The release command runs once per release on the app VM; there is no separate migration runner or rollback of a partially applied migration.