## Host Recruiting Tracker with Django: Relational Workspace Data

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

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

### Resource 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
- 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).
- An Ample account token with servers:write, databases:read.

### Tested Configuration
- **Template**: python-3.12
- **Runtime**: python
- **Size**: s-1vcpu-1gb
- **Install**: `python3 -m pip install --target .ample/python -r requirements.txt`
- **Start**: `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**: Copy the approach into your schema; keep migrations idempotent and run them with --release-command.
3. **Deploy**: Run `ample deploy . --name  --public --start "python3 run.py"`
4. **Verify**: Fetch the live URL and the pattern self-test route(s) (/p/relational-records) from the example; then run your own checks. On failure read `ample logs  --kind build` then `--kind runtime`.

### 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 recruiting tracker itself (your record schema, states, and access rules) is application code and was not separately tested; the pattern checks are what was verified.
- Apps auto-pause when idle and wake on the next request.

### Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Components**:
  - App server: s-1vcpu-1gb - $5.0
  - Managed PostgreSQL database: s-1vcpu-1gb - $5.0
- **Note**: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

### Evidence Summary
- **Canary Run**: Django pattern fixture deployed on Ample...
- **Observed at**: 2026-09-20T03:31:44Z

### Next Actions
- **Browse Catalog**: Browse the catalog index
- **Search Recipes**: Search published recipes by intent, stack and constraints