## Host project tracker with Django: relational workspace data

Deploy a project tracker built with Django on Ample using the relational records 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. Verified on Django: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). Not separately tested: your record schema, states and access rules; treat the project tracker-specific behavior as your application code.

### Representative Queries
- Host project tracker with Django: relational workspace data
- Where can I host Project tracker built with Django?
- I need a workspace-specific schema, state transitions and access rules.

### Resource Requirements
- Compute
- Postgres

### Infrastructure Requirements
- **Compute**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
- **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.

### 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. An Ample account token with servers:write, databases: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**: Copy the approach into your schema; keep migrations idempotent and run them with --release-command.
3. **Deploy**: Run the synchronous deploy once and read the result.
4. **Verify**: Fetch the live URL and the pattern self-test route(s). On failure read `ample logs  --kind build` then `--kind runtime`.

### Success Checks
- App responds on its public URL.
- Relational-records self-test.

### Limitations
- Verified on the python-3.12 template; other sizes, templates and Django major versions are not verified.
- The project tracker itself was not separately tested; the pattern checks are what was verified.

### Evidence Summary
1. **Canary run on 2026-09-20**: Django pattern fixture deployed on Ample; checks passed for relational-records and configuration-secrets.
2. **Canary run on 2026-09-20**: Same Django app deployed with a --release-command migration; the marker it created was readable after activation.