### Host documentation site with Django: bulk content imports

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

#### Representative Queries
- Host documentation site with Django: bulk content imports
- Where can I host Documentation site built with Django?
- I need a staged import format, validation procedure and import recovery workflow.

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

#### Infrastructure Requirements

1. **Compute**  
   Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
2. **Postgres**  
   Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
3. **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.
- A PostgreSQL driver reading DATABASE_URL at runtime.
- 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 bulk import staging.

3. **Wire object storage**  
   Create the bucket(s) and pass endpoint, region, bucket and keys as --env values.

4. **Deploy**  
   Run the synchronous deploy once and read the result.

5. **Verify**  
   Fetch the live URL and the pattern self-test route(s); then run your own checks.

#### Cost Estimate
- **Monthly Amount**: $10.00
- **Components**:  
   - App server: s-1vcpu-1gb, $5.00  
   - Managed PostgreSQL database: s-1vcpu-1gb, $5.00

#### Limitations
- Verified only on the python-3.12 template. Other sizes and Django major versions are not verified.

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