Host Digital Downloads with Django: Authorized File Delivery

Deploy a digital downloads 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, and 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 digital downloads-specific behavior as your application code.

Representative Queries

• Host digital downloads with Django: authorized file delivery
• Where can I host Digital downloads 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
   • 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.
2. Postgres
   • Status: Verified
   • Summary: 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
   • Status: Verified
   • Summary: 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.
• A PostgreSQL driver reading DATABASE_URL at runtime.
• A bucket created via ample bucket create with its credentials passed as encrypted S3_* environment variables.
• An Ample account token with servers:write, databases:read, 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

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: Copy the approach into your schema after ensuring migrations are idempotent.
3. Wire Object Storage: Create the bucket(s) and pass endpoint, region, bucket, and keys as --env values.
4. Deploy: Run the synchronous deploy and read the result.
5. Verify: Fetch the live URL and run your own checks.

Success Checks

1. App responds on its public URL.
2. Generated-downloads self-test.

Limitations

• Verified on the python-3.12 template; other sizes, templates, and Django major versions are not verified.
• The digital downloads itself is application code and was not separately tested.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Components:
  • App server (s-1vcpu-1gb): $5.0
  • Managed PostgreSQL database (s-1vcpu-1gb): $5.0

Evidence Summary

• Canary Run: Django pattern fixture was deployed; checks passed for generated-downloads and configuration-secrets.

Formats

• HTML format
• Markdown format

Next Actions

1. Browse the catalog index.
2. Search published recipes by intent, stack, and constraints.
3. Prepare a side-effect-free deployment plan for an authorized project.
4. Read the existing agent authentication setup.