Configure environment and secrets for Fastify · Ample Computer
Configure environment and secrets for Fastify
Configure environment variables and secrets for a Fastify app on Ample. Values passed with --env or --env-file are stored encrypted and injected at runtime; the platform never prints them and ample.toml declares only variable names. The fixture proves delivery by reporting whether the secret is set without echoing it.
Verified November 5, 2026
What it runs on
- Computeverified
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.
You need
- Code that reads configuration from the process environment
- The secret values at hand for --env or an env file
- 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
Declare, do not commit. In ample.toml declare SMTP_KEY = { secret = true } style entries; never put literal secrets in the manifest.
Pass values on deploy. Use --env KEY=value (repeatable) or --env-file .env.production; values are encrypted at rest and reused on redeploys.
$ ample deploy . --name <app-name> --public --env CANARY_SECRET=...Confirm without echoing. Expose a route (/config) that reports secret=set or secret=missing, never the value.
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
✓ app sees the configured variable without exposing it · http get/config → “secret=set”
Evidence
- November 5, 2026 · canary run
Fastify REST API using pg with no DATABASE_URL supplied: Ample auto-provisioned a managed PostgreSQL 16 database and /items reported postgres=ok after a real insert and count.
Tested examples
- Fastify secret probe canary. /config reports secret=set for an --env value delivered encrypted.
What it doesn’t cover
- Verified on the node-22 template at s-1vcpu-1gb.
- Plain env in the API request is rejected; only the encrypted path is supported.
- Rotating a secret requires a redeploy with the new value.