# Configure build and start for Fastify

Configure build and start for a Fastify app on Ample. Fastify must listen with host 0.0.0.0 on process.env.PORT. Ample detects the runtime, installs dependencies, runs the build when present and starts the app on the node-22 template behind a public HTTPS URL.

## 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.

## You need

- A package.json with build and start scripts
- A server that listens on process.env.PORT and 0.0.0.0
- An Ample account token with servers:write

## 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. **Make the start command bind correctly.** Fastify must listen with host 0.0.0.0 on process.env.PORT.

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. **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 or root route responds · http get/ → “ample canary fastify basic”

## Evidence

1. November 5, 2026 · canary run

Fastify app deployed on node-22 and served the expected response.

## Tested examples

- **fastify-basic canary.** Minimal Fastify server deployed with the detected npm commands.

## What it doesn’t cover

- Verified on the node-22 template at s-1vcpu-1gb.
