Configure environment and secrets for NestJS · Ample Computer
Configure environment and secrets for NestJS
Configuration and secrets for a NestJS app on Ample. Verified on NestJS: an --env value delivered encrypted and reported as present without being echoed (secret=set). Build and start: npm install, nest build (TypeScript) then node dist/main.js on the node-22 template.
What it runs on
- Computeverified
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.
You need
- A NestJS project (npm install, nest build (TypeScript) then node dist/main.js on the node-22 template)
- 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
Build and start. npm install, nest build (TypeScript) then node dist/main.js on the node-22 template; the server must bind 0.0.0.0 on PORT.
Pass values on deploy. Use --env KEY=value (repeatable) or --env-file; values are encrypted at rest and reused on redeploys. Declare names only in ample.toml.
$ ample deploy . --name <app-name> --public --env MY_SECRET=...Verify. Fetch the live URL and /p/configuration-secrets on the example; on failure read the build and runtime logs.
$ ample logs <deployment_id> --kind build
How it was checked
✓app responds on its public URL· http get/ → “ample canary nestjs patterns”
✓configuration-secrets check from the example· http get/p/configuration-secrets → “see the pattern fixture checks”
Evidence
- November 6, 2026 · canary run
NestJS pattern fixture deployed on Ample (npm install, nest build (TypeScript) then node dist/main.js on the node-22 template); for this guide: an --env value delivered encrypted and reported as present without being echoed (secret=set).
Tested examples
- NestJS pattern fixture. Verified configuration and secrets on NestJS.
What it doesn’t cover
- Verified on the node-22 template at s-1vcpu-1gb.