Apply database schema changes for Hono · Ample Computer

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

You need

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

What it doesn’t cover