# Host marketplace with Django: public product media

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

## Representative Queries
- Host marketplace with Django: public product media
- Where can I host Marketplace 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`

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

4. **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.

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

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

## Examples
### Django pattern fixture
- **Description:** Multi-pattern Django app whose public media library module was checked live; the module is under `tests/deploy-canaries/_pattern-modules`.
- **Source Reference:** `tests/deploy-canaries/django-patterns`

## Success Checks
- App responds on its public URL  
  - **Kind:** http_get  
  - **Path:** `/`  
  - **Expect:** ample canary django patterns
- Public-media-library self-test  
  - **Kind:** http_get  
  - **Path:** `/p/public-media-library`  
  - **Expect:** a CDN URL whose content is served publicly

## 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 marketplace 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
- **Currency:** USD
- **Monthly Amount:** 10.0  
- **Basis:** size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty.
- **Components:**
  - App server: s-1vcpu-1gb (1.0 units) - $5.00
  - Managed PostgreSQL database: s-1vcpu-1gb (1.0 units) - $5.00

## Evidence Summary
1. **Kind:** canary_run  
   - **Summary:** Django pattern fixture deployed on Ample; checks passed for public-media-library and configuration-secrets. 
   - **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; the marker it created was readable after activation.
   - **Observed At:** 2026-09-20T01:54:51Z  
   - **Expires At:** 2027-03-19T01:54:51Z

## Next Actions
1. **Browse the catalog index**  
   - **Method:** GET  
   - **Relative Path:** `/v1/catalog`
2. **Search published recipes by intent, stack and constraints**  
   - **Method:** POST  
   - **Relative Path:** `/v1/catalog/search`.
3. **Prepare a side-effect-free deployment plan for an authorized project**  
   - **Method:** POST  
   - **Relative Path:** `/v1/catalog/plan`.