Host project tracker with Next.js: relational workspace data · Ample Computer

Host project tracker with Next.js: relational workspace data

Deploy a project tracker built with Next.js on Ample using the relational records pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, a managed PostgreSQL 16 database is auto-provisioned and injected as DATABASE_URL. Verified on Next.js: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). The project tracker-specific behavior (your record schema, states and access rules) is your application code on that verified basis.

Verified November 5, 2026

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. next build then next start -H 0.0.0.0 -p $PORT on the node-22 template. The server must bind 0.0.0.0 on PORT.

  2. Implement the pattern on PostgreSQL. The fixture's module implements relational records: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.

  3. Deploy. Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 needs an answer first). Re-running with no change is a no-op.

   $ ample deploy . --name <app-name> --public
  1. Verify. Fetch the live URL and the pattern self-test route(s) (/p/relational-records) from the example; then run your own checks. On failure read ample logs <deployment_id> --kind build then --kind runtime.
   $ ample logs <deployment_id> --kind build

How it was checked

✓ app responds on its public URL · http get/ → “ample canary next js patterns”
✓ relational-records self-test · http get/p/relational-records → “records=ok transitions=true isolation=true”

Evidence

  1. November 5, 2026 · canary run
    Next.js pattern fixture deployed on Ample (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template); checks passed for relational-records and configuration-secrets. Pattern proof: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true).

  2. November 6, 2026 · canary run
    The same Next.js app deployed with a --release-command migration; the marker it created was readable after activation.

Tested examples

What it doesn’t cover