Configure environment and secrets for Starlette · Ample Computer

Configure environment and secrets for Starlette

Configuration and secrets for a Starlette app on Ample. Verified on Starlette: an --env value delivered encrypted and reported as present without being echoed (secret=set). Build and start: pip install into .ample/python from requirements.txt, then uvicorn from run.py reading PORT on the python-3.12 template.

What it runs on

You need

Exact tested configuration

installpython3 -m pip install --target .ample/python -r requirements.txt
runtimepython
sizes-1vcpu-1gb
startPYTHONPATH=.ample/python:${PYTHONPATH:-} python3 run.py
templatepython-3.12

Steps

  1. Build and start. pip install into .ample/python from requirements.txt, then uvicorn from run.py reading PORT on the python-3.12 template; the server must bind 0.0.0.0 on PORT.

  2. 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 --start "python3 run.py" --env MY_SECRET=...
    
  3. 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 starlette patterns”

✓configuration-secrets check from the example· http get/p/configuration-secrets → “see the pattern fixture checks”

Evidence

  1. November 6, 2026 · canary run
    Starlette pattern fixture deployed on Ample (pip install into .ample/python from requirements.txt, then uvicorn from run.py reading PORT on the python-3.12 template); for this guide: an --env value delivered encrypted and reported as present without being echoed (secret=set).

Tested examples

What it doesn’t cover