Host public directory with Django: public-site delivery · Ample Computer

Host public directory with Django: public-site delivery

Deploy a public directory built with Django on Ample using the public web service pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, and a published bucket serves public assets from the CDN host. Verified on Django: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL alongside the app's own public HTTPS URL. The public directory-specific behavior (your site content and build) is your application code on that verified basis.

Verified November 6, 2026

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. Build and start.
    pip install into .ample/python from requirements.txt, then waitress serving project.wsgi from run.py reading PORT on the python-3.12 template. The server must bind 0.0.0.0 on PORT.

  2. Wire object storage.
    Create the bucket(s), then pass endpoint, region, bucket and keys as --env values. Use path-style addressing. Keep private data in an unpublished bucket. Publish only the bucket that serves public assets and reference its CDN URL.

  3. Deploy.
    Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 needs an answer first). Re-running with no change is a no-op.

   $ ample deploy . --name <app-name> --public --start "python3 run.py" --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=... --env CDN_PUBLIC_URL=...  
  1. Verify.
    Fetch the live URL and the pattern self-test route(s) (/p/versioned-static-assets) from the example; then run your own checks. On failure read ample logs <deployment_id> --kind build then --kind runtime.
   $ ample logs <deployment_id> --kind build  

How it was checked

✓ app responds on its public URL · http get/ → "ample canary django patterns"

✓ versioned-static-assets self-test · http get/p/versioned-static-assets → "a CDN URL whose content is served publicly"

Evidence

  1. November 6, 2026 · canary run
    Django pattern fixture deployed on Ample (pip install into .ample/python from requirements.txt, then waitress serving project.wsgi from run.py reading PORT on the python-3.12 template); checks passed for versioned-static-assets and configuration-secrets. Pattern proof: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL alongside the app's own public HTTPS URL.

  2. November 6, 2026 · canary run
    The same Django app deployed with a --release-command migration; the marker it created was readable after activation.

Tested examples

What it doesn’t cover