Apply database schema changes for NestJS · Ample Computer

Apply database schema changes for NestJS

Schema changes for a NestJS app on Ample. Verified on NestJS: a --release-command migration ran before activation and its marker was readable by the live app (migrated=release-ok). Build and start: npm install, nest build (TypeScript) then node dist/main.js on the node-22 template.

What it runs on

You need

Exact tested configuration

Steps

  1. Build and start. npm install, nest build (TypeScript) then node dist/main.js 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"
  1. 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 nestjs patterns”
✓ migrated check from the example · http get/p/migrated → “see the pattern fixture checks”

Evidence

  1. November 6, 2026 · canary run
    NestJS pattern fixture deployed on Ample (npm install, nest build (TypeScript) then node dist/main.js 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