Apply database schema changes for Fastify · Ample Computer

Apply database schema changes for Fastify

Apply database schema changes for a Fastify app on Ample with a release command. node migrate.js 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

build npm run build --if-present

install npm install

runtime node

sizes-1vcpu-1gb

start npm run start

template node-22

Steps

  1. Write an idempotent migration. Create tables and markers with IF NOT EXISTS or a migration framework 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 (/migrated) 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 6, 2026 · canary run

The same Fastify app deployed with --release-command node migrate.js against its auto-provisioned managed database; /migrated reported the marker the migration created.

Tested examples

What it doesn’t cover