# Host recruiting tracker with FastAPI: relational workspace data

Deploy a recruiting tracker built with FastAPI 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 FastAPI: 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.

## Summary
- **Framework:** FastAPI  
- **Workload:** Recruiting tracker  
- **Release Status:** published  
- **Support Status:** verified  
- **Execution Status:** ready  
- **Docs Only:** false

## Prerequisites
- A FastAPI project that builds and starts with the documented commands (pip install into .ample/python from requirements.txt, then uvicorn 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).
- An Ample account token with servers:write, databases:read.

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

## Workflow Steps
1. **Build and Start**  
   - pip install into .ample/python from requirements.txt, then uvicorn 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 relational records: 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). 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 (exit 0 live, 1 failed, 2 blocked). Re-running with no change is a no-op.
   - **Command:** 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`.
   - **Command:** ample logs  --kind build.

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

## Examples
- **Title:** FastAPI pattern fixture  
  **Description:** Multi-pattern FastAPI app whose relational records module was checked live; the module is under tests/deploy-canaries/_pattern-modules.  
  **Source Ref:** tests/deploy-canaries/fastapi-patterns

## Success Checks
- **App responds on its public URL**  
  - **Kind:** http_get  
  - **Path:** /  
  - **Expect:** ample canary fastapi patterns  
- **Relational-records self-test**  
  - **Kind:** http_get  
  - **Path:** /p/relational-records  
  - **Expect:** records=ok transitions=true isolation=true

## Limitations
- Verified on the python-3.12 template at s-1vcpu-1gb with the example fixture; other sizes, templates and FastAPI 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.
- Region, compliance attestations and request-duration limits are unknown and not claimed.
- Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.

## Cost Estimate
- **Currency:** USD
- **Monthly Amount:** 10.0
- **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.
- **Components:**
  - **App server:** size: s-1vcpu-1gb, quantity: 1.0, monthly amount: 5.0.
  - **Managed PostgreSQL database:** size: s-1vcpu-1gb, quantity: 1.0, monthly amount: 5.0.

## Formats
- **HTML:** [Link](/content/recipes/recruiting-tracker/fastapi/relational-workspace/index.html)
- **Markdown:** [Link](/content/recipes/recruiting-tracker/fastapi/relational-workspace.md)
- **JSON:** [Link](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Arecruiting-tracker%3Afastapi%3Arelational-workspace)