Configure build and start for Next.js · Ample Computer

Configure build and start for Next.js

Configure build and start for a Next.js app on Ample. A server-rendered app runs next build then next start on the node-22 template with the detected package manager; a static export is published as a static site. The app must bind 0.0.0.0 on PORT.

Verified November 6, 2026

What it runs on

You need

Exact tested configuration

Steps

  1. Make next start listen correctly. Use next start -H 0.0.0.0 -p ${PORT:-3000} so the health check reaches the server.

  2. Deploy. Run the existing synchronous deploy once from the project directory and read the result. Exit 0 is live, 1 is failed, 2 needs an answer first (a preflight question). Re-running with no change is a content-addressed no-op.

    $ ample deploy . --name <app-name> --public --format json  
    
  3. Static exports. With output: 'export' the build is published as a static site with correct 404 handling; no server process runs.

  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.

    $ ample logs <deployment_id> --kind build  
    

How it was checked

✓ page renders · http get/ → “ample canary next basic ssr”
✓ API route stays a Next route · http get/api/canary → “next api stays next”

Evidence

  1. November 6, 2026 · canary run
    Next.js 15 SSR app (next build, next start) deployed on node-22; the page and an API route served correctly.
  2. November 6, 2026 · canary run
    Next.js app using pnpm deployed with the detected package manager.
  3. November 6, 2026 · canary run
    Next.js static export (Vercel-style output) was published and served, including a nested route and a correct 404.

Tested examples

What it doesn’t cover