page:recipes:order tracking:django:download delivery

Host order tracking with Django: authorized file delivery

Deploy an order tracking built with Django on Ample using the generated downloads pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, a managed PostgreSQL 16 database is auto-provisioned and injected as DATABASE_URL, a private S3-compatible bucket holds objects with credentials delivered as encrypted environment variables. Verified on Django: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). Not separately tested: your export formats, retention policy and entitlement model; treat the order tracking-specific behavior as your application code.

Representative Queries

• Host order tracking with Django: authorized file delivery
• Where can I host Order tracking built with Django?
• I need a file entitlement model and an application-enforced download authorization flow.

Resource Requirements

• primitive:compute
• primitive:postgres
• primitive:s3-compatible-object-storage

Infrastructure Requirements

1. Compute
   Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
2. Postgres
   Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
3. S3-compatible object storage
   Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

Prerequisites

• 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)
• A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)
• A bucket from ample bucket create with its credentials passed as encrypted S3_* environment variables
• An Ample account token with servers:write, databases:read, buckets:read

Workflow 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. Implement the pattern on PostgreSQL
   The fixture's module implements generated downloads: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.
3. 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.
4. 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.
5. Verify
   Fetch the live URL and the pattern self-test route(s) (/p/generated-downloads) from the example; then run your own checks. On failure read ample logs --kind build then --kind runtime.

Examples

• Django pattern fixture
  Multi-pattern Django app whose generated downloads module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

Success Checks

1. App responds on its public URL
   Expected: ample canary django patterns
2. Generated-downloads self-test
   Expected: export=ok rows=3 (with ?token=...; 401 without)

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 order tracking itself (your export formats, retention policy and entitlement model) 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.
• Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.
• PutObject and GetObject with path-style addressing are verified; multipart upload, listing, presigned URLs and lifecycle rules are not.

Cost Estimate

• Currency: USD
• Monthly Amount: $10.00
• Authority: true
• Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
• Components:
  • App server (s-1vcpu-1gb) : $5.00
  • Managed PostgreSQL database (s-1vcpu-1gb) : $5.00
• 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

• Canary Run
  Django pattern fixture deployed on Ample; checks passed for generated-downloads and configuration-secrets.
  • Observed At: 2026-09-20T03:31:44Z
  • Implementation Revision: 03b6402b1b3e19178985f08ea4033804521d85d4-dirty
  • Expires At: 2027-03-19T03:31:44Z
  • Scope: checks=[/p/generated-downloads], pattern=pattern:generated-downloads, template=python-3.12
• Canary Run
  The same Django app deployed with a --release-command migration; the marker it created was readable after activation.
  • Observed At: 2026-09-20T01:54:51Z
  • Implementation Revision: 199ff1dfd52683832ae75d3f98b53a7a4bff7f96-dirty
  • Expires At: 2027-03-19T01:54:51Z
  • Scope: pattern=pattern:generated-downloads

Next Actions

• Browse the catalog index
  • Method: GET
  • Relative Path: /v1/catalog
• Search published recipes by intent, stack and constraints
  • Method: POST
  • Relative Path: /v1/catalog/search
  • Body: {"limit": 5, "query": "Host order tracking with Django: authorized file delivery"}
• Prepare a side-effect-free deployment plan for an authorized project
  • Method: POST
  • Relative Path: /v1/catalog/plan
  • Body: {"inputs": {}, "projectId": "", "recipeId": "page:recipes:order-tracking:django:download-delivery", "recipeRevision": "r1"}
• Read the existing agent authentication setup
  • Method: GET
  • Relative Path: /mcp/setup
• Browse Order tracking
  • Method: GET
  • Relative Path: /v1/catalog/nodes/workload%3Aorder-tracking
• Browse Django
  • Method: GET
  • Relative Path: /v1/catalog/nodes/stack%3Aframework-django
• Browse Generated downloads
  • Method: GET
  • Relative Path: /v1/catalog/nodes/pattern%3Agenerated-downloads
• Browse Deploy web app
  • Method: GET
  • Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app