## Host CRM with Django: Private Attachments

### Summary
Deploy a CRM built with Django on Ample using the private document 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. Verified on Django: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok). Not separately tested: your identity integration and role assignments; treat the crm-specific behavior as your application code.

### Workload Recipe
- **Framework:** Django  
- **Workload:** CRM  
- **Release Status:** Published  
- **Support Status:** Verified  
- **Execution Status:** Ready

### Representative Queries
- Host crm with Django: private attachments  
- Where can I host CRM built with Django?  
- I need attachment metadata, access checks and a tested private object access path.

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

### Infrastructure Requirements
1. **Compute**  
   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**  
   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**  
   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 (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
- An Ample account token with servers:write, databases:read, buckets:read

### Tested Configuration
- **Template:** python-3.12  
- **Runtime:** python  
- **Size:** s-1vcpu-1gb  
- **Install command:** python3 -m pip install --target .ample/python -r requirements.txt  
- **Start command:** 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**  
   The fixture's module implements private document library: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok).  
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). Re-running with no change is a no-op.
5. **Verify**  
   Fetch the live URL and the pattern self-test route(s) (/p/private-document-library) from the example; then run your own checks.

### Examples
- **Django Pattern Fixture:** Multi-pattern Django app whose private document library module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

### Success Checks
1. **App responds on its public URL**  
   - Kind: http_get  
   - Path: /  
   - Expect: ample canary django patterns  
2. **Private-document-library self-test**  
   - Kind: http_get  
   - Path: /p/private-document-library  
   - Expect: private=ok (with ?role=owner; 401 without, 403 for viewer)

### 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 crm itself (your identity integration and role assignments) 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.

### Cost Estimate
- **Monthly Amount:** $10.00  
- **Components:**  
  - App server: s-1vcpu-1gb, $5.00  
  - Managed PostgreSQL database: s-1vcpu-1gb, $5.00
- **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.