page:recipes:recruiting tracker:fastapi:report exports

Host Recruiting Tracker with FastAPI: Downloadable Reports

Deploy a recruiting tracker built with FastAPI on Ample using the generated downloads 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 FastAPI: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). Not separately tested: your export formats, retention policy and entitlement model; treat the recruiting tracker-specific behavior as your application code.

Representative Queries

• Host recruiting tracker with FastAPI: downloadable reports
• Where can I host Recruiting tracker built with FastAPI?
• I need an export query, generated artifact retention and authorized download flow.

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.

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: Copy the approach into your schema; keep migrations idempotent and run them with --release-command.
3. Wire object storage: Create the bucket(s), then pass endpoint, region, bucket, and keys as --env values.
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.

Example

• Title: FastAPI pattern fixture
• Description: Multi-pattern FastAPI app whose generated downloads module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
• Source Reference: tests/deploy-canaries/fastapi-patterns

Success Checks

• app responds on its public URL: / expects response: ample canary fastapi patterns.
• generated-downloads self-test: /p/generated-downloads expects export=ok rows=3 (with ?token=...; 401 without).

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 export formats, retention policy, and entitlement model) was not separately tested; the pattern checks are what was verified.