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
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 no DATABASE_URL is supplied.
You need
A NestJS project (npm install, nest build (TypeScript) then node dist/main.js on the node-22 template)
A PostgreSQL driver reading DATABASE_URL at runtime
An Ample account token with servers:write, databases:read
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
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.
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"
- 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
- 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
- NestJS pattern fixture. Verified schema changes on NestJS.
What it doesn’t cover
- Verified on the node-22 template at s-1vcpu-1gb.
- Managed PostgreSQL 16 with pgvector.