Configure environment and secrets for Nuxt · Ample Computer

Configure environment and secrets for Nuxt

Configure environment variables and secrets for a Nuxt 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.

What it runs on

You need

Exact tested configuration

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 reused on redeploys.

    $ ample deploy . --name <app-name> --public --env CANARY_SECRET=...  
    ```

3. **Confirm without echoing.** Expose a route (/api/config) that reports secret=set or secret=missing, never the value.

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.
$ ample logs <deployment_id> --kind build  
```

How it was checked

✓app sees the configured variable without exposing it· http get/api/config → “secret=set”

Evidence

  1. November 6, 2026 · canary run

Nuxt server routes using pg with an auto-provisioned managed PostgreSQL database: /api/db reported postgres=ok and /api/config confirmed an encrypted secret was delivered without echoing it.

Tested examples

What it doesn’t cover