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. Not separately tested: your site content and build; treat the public directory-specific behavior as your application code.

Representative Queries

• Host public directory with Django: public-site delivery
• Where can I host Public directory built with Django?
• I need an explicit origin-to-CDN delivery path and a tested public content build.

Resource Requirements

• primitive:compute
• primitive:cdn

Infrastructure Requirements

Compute

• ID: primitive:compute
• Label: Compute
• Status: verified
• Summary: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.

CDN

• ID: primitive:cdn
• Label: CDN
• Status: verified
• Summary: The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.

Prerequisites

1. A Django project that builds and starts with the documented commands (pip install into .ample/python from requirements.txt, then waitress serving project.wsgi from run.py reading PORT on the python-3.12 template)
2. A bucket from ample bucket create with its credentials passed as encrypted S3_* environment variables
3. An Ample account token with servers:write, buckets:read

Tested Configuration

• Template: python-3.12
• Runtime: python
• Size: s-1vcpu-1gb
• Install: python3 -m pip install --target .ample/python -r requirements.txt
• Start: PYTHONPATH=.ample/python:${PYTHONPATH:-} python3 run.py

Workflow Steps

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

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

Step 3: Deploy

• Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 blocked). Re-running with no change is a no-op.
  Command: ample deploy . --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=...

Step 4: 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 --kind build then --kind runtime.
  Command: ample logs --kind build

Limitations

• Verified on the python-3.12 template at s-1vcpu-1gb with the example fixture; other sizes, templates and Django major versions are not verified.
• The public directory itself (your site content and build) is application code and was not separately tested; the pattern checks are what was verified.
• Region, compliance attestations and request-duration limits are unknown and not claimed.
• Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.
• PutObject and GetObject with path-style addressing are verified; multipart upload, listing, presigned URLs and lifecycle rules are not.
• The CDN serves published-bucket objects only; cache rules, purge and TTL control are not verified (the fixture sets Cache-Control on upload and versions keys).

Cost Estimate

• Currency: USD
• Monthly Amount: 5.0
• Basis: size prices from pricing.toml at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
• Components:
  • Name: app server
  • Size: s-1vcpu-1gb
  • Quantity: 1.0
  • Monthly Amount: 5.0
• Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

Evidence Summary

• Summary: 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.
• Observed At: 2026-09-20T03:31:44Z
• Implementation Revision: 03b6402b1b3e19178985f08ea4033804521d85d4-dirty (CLI b75e104)
• Expires At: 2027-03-19T03:31:44Z
• Scope:
  • Checks: [/p/versioned-static-assets]
  • Pattern: pattern:public-web-service
  • Template: python-3.12

Next Actions

• Action: Browse the catalog index

• Operation ID: catalog_index

• Method: GET

• Relative Path: /v1/catalog

• Action: Search published recipes by intent, stack and constraints

• Operation ID: search_recipes

• Method: POST

• Relative Path: /v1/catalog/search

• Parameters: {"body":{"limit":5,"query":"Host public directory with Django: public-site delivery"}}

• Action: Prepare a side-effect-free deployment plan for an authorized project

• Operation ID: plan_deployment

• Method: POST

• Relative Path: /v1/catalog/plan

• Parameters: {"body":{"inputs":{},"projectId":"","recipeId":"page:recipes:public-directory:django:public-site","recipeRevision":"r1"}}

• Action: Read the existing agent authentication setup

• Operation ID: existing_auth_setup

• Method: GET

• Relative Path: /mcp/setup

• Action: Browse Public directory

• Operation ID: browse_node

• Method: GET

• Relative Path: /v1/catalog/nodes/workload%3Apublic-directory

• Parameters: {"nodeId":"workload:public-directory"}

• Action: Browse Django

• Operation ID: browse_node

• Method: GET

• Relative Path: /v1/catalog/nodes/stack%3Aframework-django

• Parameters: {"nodeId":"stack:framework-django"}

• Action: Browse Public web service

• Operation ID: browse_node

• Method: GET

• Relative Path: /v1/catalog/nodes/pattern%3Apublic-web-service

• Parameters: {"nodeId":"pattern:public-web-service"}

• Action: Browse Deploy web app

• Operation ID: browse_node

• Method: GET

• Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app

• Parameters: {"nodeId":"intent:deploy-web-app"}