# Host Approval Workflow with Django: Private Attachments

Deploy an approval workflow 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 approval workflow-specific behavior as your application code.

## Summary
- **Framework**: Django
- **Workload**: Approval workflow
- **Release Status**: published
- **Support Status**: verified
- **Execution Status**: ready

## Prerequisites
1. 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)
2. A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)
3. A bucket from `ample bucket create` with its credentials passed as encrypted S3_* environment variables
4. An Ample account token with servers:write, databases:read, buckets:read

## Resource Requirements
- **Compute**
- **Postgres**
- **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.

## Input Schema
- `env`: Encrypted environment variables (bucket credentials, secrets)
- `name`: App name (maxLength: 63, minLength: 1)
- `path`: Project directory or ample.toml service (maxLength: 512, minLength: 1)
- `release_command`: Migration command run before activation (maxLength: 512)
- `start`: Start command (maxLength: 512)

## 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 a private document library with tests.
3. **Wire object storage**: Create bucket(s) and configure environment variables.
4. **Deploy**: Run synchronous deploy and read result.
5. **Verify**: Fetch live URL and run checks.

## Examples
- **Django pattern fixture**: Multi-pattern Django app whose private document library module was checked live.

## Limitations
- Verified on the python-3.12 template at s-1vcpu-1gb; other sizes are not verified.
- The approval workflow itself (identity integration and role assignments) is application code and was not separately tested.

## Cost Estimate
- **Monthly Amount**: $10.00
- **Components**:
  - App server (1): $5.00
  - Managed PostgreSQL database (1): $5.00

## Success Checks
1. App responds on its public URL
2. Private-document-library self-test

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

## Evidence Summary
- Canary run deployment summary with checks passed for private-document-library.

## Unknowns
- Region availability is unknown until verified.
- Compliance attestations are unknown; none are claimed.