Apply database schema changes for Next.js · Ample Computer

Apply database schema changes for Next.js

Schema Changes

Schema changes for a Next.js app on Ample. Verified on Next.js: a --release-command migration ran before activation and its marker was readable by the live app (migrated=release-ok). Build and start: next build then next start -H 0.0.0.0 -p $PORT on the node-22 template.

What it runs on

You need

Exact Tested Configuration

Steps

  1. Build and start. next build then next start -H 0.0.0.0 -p $PORT on the node-22 template; the server must bind 0.0.0.0 on PORT.

  2. Run migrations as the release command. Ample runs the command before activation and fails the release if it exits non-zero; keep migrations idempotent.

    $ ample deploy . --name <app-name> --public --release-command "node migrate.cjs"
    
  3. Verify. Fetch the live URL and /p/migrated on the example; on failure read the build and runtime logs.

    $ ample logs <deployment_id> --kind build
    

How it was checked

✓ app responds on its public URL· http get/ → "ample canary next js patterns"

✓ migrated check from the example· http get/p/migrated → "see the pattern fixture checks"

Evidence

  1. November 5, 2026 · canary run

    Next.js pattern fixture deployed on Ample (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template); for this guide: a --release-command migration ran before activation and its marker was readable by the live app (migrated=release-ok).

Tested Examples

What it doesn’t cover