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

You need

Exact tested configuration

Steps

  1. Write an idempotent migration. Create tables and markers with IF NOT EXISTS or a migration tool so a re-run is safe.

  2. 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"
  1. Verify the marker through the app. Serve a route that reads something only the migration creates.

  2. 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

  1. November 5, 2026 · canary run
    A --release-command migration ran before the release went live; /migrated reported the marker the migration created.

  2. November 6, 2026 · canary run
    Express app with npm install and npm run start deployed on the node-22 template; the public URL served the expected response.

Tested examples

What it doesn’t cover