### Host campaign site with Django: Postgres-backed content

Deploy a campaign site built with Django on Ample using the relational records 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 published bucket serves public assets from the CDN host. Verified on Django: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). Not separately tested: your record schema, states and access rules; treat the campaign site-specific behavior as your application code.

#### Representative Queries
- Host campaign site with Django: Postgres-backed content
- Where can I host Campaign site built with Django?
- I need a content schema, publishing workflow and cache behavior after content updates.

#### Resource Requirements
- **Compute**  
- **Postgres**  
- **CDN**

#### 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. **CDN**  
   - **Status:** verified  
   - **Summary:** The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.

#### 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 relational records: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). 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/relational-records) from the example; then run your own checks. On failure read `ample logs  --kind build` then `--kind runtime`.*  
   - Command: `ample logs  --kind build`

#### 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 campaign site itself (your record schema, states and access rules) 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.
- The CDN serves published-bucket objects only; cache rules, purge and TTL control are not verified (the fixture sets Cache-Control on upload and versions keys).

#### Cost Estimate
- **Monthly Amount:** $10.00  
- **Basis:** size prices from pricing.toml (loaded by the API) at build revision...  
- **Components:**  
  - App server (size s-1vcpu-1gb): $5.00  
  - Managed PostgreSQL database (size s-1vcpu-1gb): $5.00  
- *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. **Canary Run**  
   - Summary: Django pattern fixture deployed on Ample...  
   - Observed At: 2026-09-20T03:31:44Z

2. **Canary Run**  
   - Summary: 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

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