Configure environment and secrets for Django · Ample Computer

Configure environment and secrets for Django

Configure environment variables and secrets for a Django 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 run.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 run.py" --env CANARY_SECRET=...
  1. Confirm without echoing. Expose a route (/config) that reports secret=set or secret=missing, never the value.

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

  1. November 6, 2026 · canary run

Django 5 project with dj-database-url and psycopg: the managed PostgreSQL database was auto-provisioned, python3 manage.py migrate ran as the release command, and /db and /migrated reported postgres=ok and the migrated marker.

Tested examples

What it doesn’t cover