# Host form collection with Django: data exports

Deploy a form collection 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 form collection-specific behavior as your application code.

## Representative Queries
- Host form collection with Django: data exports
- Where can I host Form collection built with Django?
- I need a scoped export format, artifact generation and authorized download procedure.

## Resource Requirements
- primitive:compute
- primitive:postgres
- primitive:s3-compatible-object-storage

## Infrastructure Requirements
- **Compute**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
- **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.
- **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`.

## Success Checks
- `app responds on its public URL`: Path: `/`, Expect: `ample canary django patterns`
- `generated-downloads self-test`: Path: `/p/generated-downloads`, Expect: `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 form collection 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.
- Applications auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.

## Cost Estimate
- **Monthly Amount**: $10.00 (USD)  
- Basis: Size prices from pricing.toml at build revision `1ac5595375130d45290090e82ed0f554ccd45405-dirty`.

### Breakdown
- **app server** (size: s-1vcpu-1gb, quantity: 1.0): $5.00
- **managed PostgreSQL database** (size: s-1vcpu-1gb, quantity: 1.0): $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.

## Next Actions
- **Browse the catalog index**: GET `/v1/catalog`
- **Search published recipes**: POST `/v1/catalog/search`
- **Prepare deployment plan**: POST `/v1/catalog/plan`  
- **Read existing authentication setup**: GET `/mcp/setup`  
- **Browse Form collection**: GET `/v1/catalog/nodes/workload%3Aform-collection`
- **Browse Django**: GET `/v1/catalog/nodes/stack%3Aframework-django`  
- **Browse Generated downloads**: GET `/v1/catalog/nodes/pattern%3Agenerated-downloads`  
- **Browse Deploy web app**: GET `/v1/catalog/nodes/intent%3Adeploy-web-app`