# Configure environment and secrets for Express

Configure environment variables and secrets for an Express 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 the variable names.

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

- Code that reads configuration from process.env
- The secret values at hand for --env or an env file
- An Ample account token with servers:write

## Exact tested configuration

```bash
buildnpm run build --if-present
installnpm install
runtimenode
sizes-1vcpu-1gb
startnode server.js
templatenode-22
```

## Steps

1.  **Declare, do not commit.** In ample.toml declare SMTP\_KEY = { secret = true } style entries; never put literal secrets in the manifest.

2.  **Pass values on deploy.** Use --env KEY=value (repeatable) or --env-file .env.production; values are encrypted at rest and re-used on redeploys.

```bash
   $ ample deploy . --name <app-name> --public --env DATABASE_URL=postgres://...
   ```

3.  **Confirm without echoing.** Expose a route that reports which variables are set (host names, not values) and check it.

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.

```bash
   $ ample logs <deployment_id> --kind build
   ```

## How it was checked

✓app sees the configured variable without exposing it· http get/db → “secret=false”

## Evidence

1. November 6, 2026 · canary run  
A supplied DATABASE\_URL was delivered as an encrypted environment variable; the app saw the configured host and the secret was never echoed by the platform.

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

-  **Encrypted DATABASE\_URL canary.** /db reports the configured host with secret=false, proving delivery without disclosure.

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