Configure environment and secrets for Flask · Ample Computer

Configure environment and secrets for Flask

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

install python3 -m pip install --target .ample/python -r requirements.txt
runtime python
sizes -1vcpu-1gb
start PYTHONPATH=.ample/python:${PYTHONPATH:-} python3 app.py
template python-3.12

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 --start "python3 app.py" --env CANARY_SECRET=...
    ```

3. **Confirm without echoing.** Expose a route (/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.

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

## How it was checked

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

## Evidence

1. November 6, 2026 · canary run  
   Flask app (waitress) using psycopg with an auto-provisioned managed PostgreSQL database: /items reported postgres=ok and /config confirmed the encrypted secret.

## Tested examples

- **Flask secret probe canary.** /config reports secret=set for an --env value delivered encrypted.

## What it doesn’t cover

- Verified on the python-3.12 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.