Configure build and start for Express · Ample Computer
Configure build and start for Express
Configure build and start for an Express app on Ample. Ample detects Node, runs npm install and npm run build --if-present, and starts the app with npm run start on the node-22 template; the app only has to bind 0.0.0.0 on PORT.
Verified November 6, 2026
What it runs on
- Computeverified
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.
You need
- A package.json with a start script
- A server that listens on process.env.PORT and 0.0.0.0
- An Ample account token with servers:write
Exact tested configuration
- build: echo no build needed
- install: npm install
- runtime: node
- sizes: 1vcpu-1gb
- start: npm run start
- template: node-22
Steps
Pin what detection cannot infer. If the start command is not in package.json, pass --start, or write it into ample.toml with ample plan --write.
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 jsonVerify. 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
✓ root route responds · http get/ → “ample canary express basic”
Evidence
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
- Express basic canary. Minimal Express server deployed with the detected npm install / npm run start commands.
What it doesn’t cover
- Verified on the node-22 template at s-1vcpu-1gb.
- A missing package-lock.json produces a warning and a slower, non-reproducible install.