## Host admin dashboard with Django: public profile assets

### Summary
Deploy an admin dashboard built with Django on Ample using the public image delivery 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: public objects in a published bucket served from the CDN URL, kept separate from private objects in an unpublished bucket that require authorization (private=ok only for the allowed role). Not separately tested: your image processing and profile-media rules; treat the admin dashboard-specific behavior as your application code.

### Representative Queries
- Host admin dashboard with Django: public profile assets
- Where can I host Admin dashboard built with Django?
- I need separate public profile media from private data, with CDN cache rules.

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

### Framework
Django

### Workload
Admin dashboard

### Release Status
Published

### Support Status
Verified

### Execution Status
Ready

### 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
- 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 image delivery: public objects in a published bucket served from the CDN URL, kept separate from private objects in an unpublished bucket that require authorization (private=ok only for the allowed role). Copy the approach into your schema.
3. **Wire object storage**
   - Create the bucket(s), then pass endpoint, region, bucket and keys as --env values. Use path-style addressing.
4. **Deploy**
   - Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 blocked).
5. **Verify**
   - Fetch the live URL and the pattern self-test route(s) from the example; then run your own checks.

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

### Limitations
- Verified on the python-3.12 template at s-1vcpu-1gb; other sizes, templates are not verified.
- The admin dashboard itself (your image processing and profile-media rules) is application code and was not separately tested.
- Region, compliance attestations and request-duration limits are unknown.
- Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.

### Cost Estimate
- **Monthly Amount**: $10.00
- **Basis**: size prices from pricing.toml 
  - **Components**:
    - App server: s-1vcpu-1gb - $5.00
    - Managed PostgreSQL database: s-1vcpu-1gb - $5.00

### Evidence Summary
- **Kind**: Canary run
- **Summary**: Django pattern fixture deployed on Ample; checks passed for public-media-library, private-document-library and configuration-secrets.

### Last Verified At
2026-09-20T03:31:44Z

### Formats
- **HTML**: [Link](/content/recipes/admin-dashboard/django/public-profiles/index.html)
- **Markdown**: [Link](/content/recipes/admin-dashboard/django/public-profiles.md)
- **JSON**: [Link](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Aadmin-dashboard%3Adjango%3Apublic-profiles)

### Next Actions
1. **Browse the catalog index**
2. **Search published recipes by intent, stack and constraints**
3. **Prepare a side-effect-free deployment plan for an authorized project**
4. **Read the existing agent authentication setup**
5. **Browse Admin dashboard**
6. **Browse Django**
7. **Browse Public image delivery**
8. **Browse Deploy web app**