# Host digital downloads with Django: inventory imports

## Summary
Deploy a digital downloads built with Django on Ample using the bulk import staging 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: a CSV staged as an object, row-level validation with per-row errors recorded, and a restart-safe import keyed by import id (imported=2 rejected=1 restart=ok). Not separately tested: your import format, mapping and conflict rules; treat the digital downloads-specific behavior as your application code.

## Representative Queries
- Host digital downloads with Django: inventory imports
- Where can I host Digital downloads built with Django?
- I need an inventory import contract, staging objects and row-level error handling.

## 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
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 PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env).
3. A bucket from `ample bucket create` with its credentials passed as encrypted S3_* environment variables.
4. 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**: 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).
5. **Verify**: Fetch the live URL and the pattern self-test route(s) (/p/bulk-import-staging) from the example; then run your own checks.

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

## 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`

## Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Basis**: size prices from pricing.toml
- **Components**:
  - App server: s-1vcpu-1gb - 1.0 monthlyAmount: 5.0
  - Managed PostgreSQL database: s-1vcpu-1gb - 1.0 monthlyAmount: 5.0

## Success Checks
- **App responds on its public URL**: `ample canary django patterns`
- **Bulk-import-staging self-test**: `imported=2 rejected=1 restart=ok`

## Evidence Summary
- **Canary run**: Django pattern fixture deployed on Ample, checks passed.
- **Canary run**: The same Django app deployed with a --release-command migration; the marker it created was readable after activation.

## 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
