# 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

- [Computeverified](/content/discover/primitive/compute/index.html)  
  Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

- [Postgresverified](/content/discover/primitive/postgres/index.html)  
  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 migration script that reads `process.env.DATABASE_URL` and exits non-zero on failure
- A PostgreSQL database (supplied or managed)
- An Ample account token with `servers:write` and `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

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.
   
   ```bash
   $ ample deploy . --name <app-name> --public --release-command "node migrate.js"
   ```

3.  **Verify the marker through the app.** Serve a route that reads something only the migration creates.

4.  **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.
   
   ```bash
   $ 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

-  **Release-command migration canary.** `node migrate.js` creates a marker table before activation; `/migrated` reads it.

## What it doesn’t cover

-  Verified on the `node-22` template at `s-1vcpu-1gb`.
-  Managed PostgreSQL 16 with pgvector.
-  Apps and their managed databases are placed together, in the same region.
-  The release command runs once per release on the app VM; there is no separate migration runner or rollback of a partially applied migration.
