# Host order tracking with Django: public product media

Deploy a order tracking built with Django on Ample using the public media library 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, and a published bucket serves public assets from the CDN host. Verified on Django: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly. Not separately tested: your media processing, object layout and cache policy; treat the order tracking-specific behavior as your application code.

## Representative Queries
- Host order tracking with Django: public product media
- Where can I host Order tracking built with Django?
- I need product-to-object mappings and a tested public media delivery path.

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

## Framework
Django

## Workload
Order tracking

## 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 and a second, published bucket for public assets (CDN_*)
- 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 public media library: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly. 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. Publish only the bucket that serves public assets and reference its CDN URL.
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.
   
   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=...`
5. **Verify**  
Fetch the live URL and the pattern self-test route(s) (/p/public-media-library) from the example; then run your own checks. On failure read `ample logs  --kind build` then `--kind runtime`. 
   
   Command: `ample logs  --kind build`

## Success Checks
- App responds on its public URL
- Public-media-library self-test

## 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 media processing, object layout and cache policy) is application code and was not separately tested; the pattern checks are what was verified.

## Cost Estimate
```json
{
  "currency": "USD",
  "monthlyAmount": 10.0,
  "basis": "size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty",
  "components": [
    {
      "name": "app server",
      "size": "s-1vcpu-1gb",
      "quantity": 1.0,
      "monthlyAmount": 5.0
    },
    {
      "name": "managed PostgreSQL database",
      "size": "s-1vcpu-1gb",
      "quantity": 1.0,
      "monthlyAmount": 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
1. Kind: Canary Run  
   Summary: Django pattern fixture deployed on Ample...  
   Observed At: 2026-09-20T03:31:44Z
   Expires At: 2027-03-19T03:31:44Z  
2. Kind: Canary Run  
   Summary: The same Django app deployed with a --release-command migration...  
   Observed At: 2026-09-20T01:54:51Z
   Expires At: 2027-03-19T01:54:51Z

## Next Actions
- **Browse the catalog index**  
- **Search published recipes by intent, stack and constraints**  
- **Prepare a side-effect-free deployment plan for an authorized project**  
- **Read the existing agent authentication setup**  
- **Browse Order tracking**  
- **Browse Django**  
- **Browse Public media library**  
- **Browse Deploy web app**

### Formats
- [HTML](/content/recipes/order-tracking/django/product-media/index.html) 
- [Markdown](/content/recipes/order-tracking/django/product-media.md) 
- [JSON](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Aorder-tracking%3Adjango%3Aproduct-media)