# Apply database schema changes for Hono

Schema changes for a Hono app on Ample. Verified on Hono: a --release-command migration ran before activation and its marker was readable by the live app (migrated=release-ok). Build and start: npm install and npm run start with @hono/node-server on the node-22 template.

## 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 Hono project (npm install and npm run start with @hono/node-server 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

1.  **Build and start.** npm install and npm run start with @hono/node-server 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 hono patterns”  
✓migrated check from the example· http get/p/migrated → “see the pattern fixture checks”

## Evidence

1. November 6, 2026 · canary run  
   Hono pattern fixture deployed on Ample (npm install and npm run start with @hono/node-server 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

- **Hono pattern fixture.** Verified schema changes on Hono.

## What it doesn’t cover

- Verified on the node-22 template at s-1vcpu-1gb.
- Managed PostgreSQL 16 with pgvector.
