## Host Recruiting Tracker with Flask: Downloadable Reports

Deploy a recruiting tracker built with Flask 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 Flask: 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 Flask: downloadable reports
- Where can I host Recruiting tracker built with Flask?
- I need an export query, generated artifact retention and authorized download flow.

### Resource Requirements
- primitive:compute
- primitive:postgres
- primitive:s3-compatible-object-storage

### 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.
- **S3-compatible object storage**: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

### Framework
Flask

### Workload
Recruiting tracker

### Execution Status
Ready

### Prerequisites
1. A Flask project that builds and starts with the documented commands (pip install into .ample/python from requirements.txt, then waitress from app.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

### Workflow Steps
- **Build and start**: `pip install into .ample/python from requirements.txt, then waitress from app.py reading PORT on the python-3.12 template. The server must bind 0.0.0.0 on PORT.`
- **Implement the pattern on PostgreSQL**: The fixture's module implements generated downloads: 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). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.
- **Wire object storage**: Create the bucket(s), then pass endpoint, region, bucket and keys as --env values. Use path-style addressing. Keep private data in an unpublished bucket.
- **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 app.py" --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...`
- **Verify**: Fetch the live URL and the pattern self-test route(s) (/p/generated-downloads) from the example; then run your own checks. On failure read `ample logs  --kind build` then `--kind runtime`.
  - Command: `ample logs  --kind build`

### Examples
- **Flask pattern fixture**: Multi-pattern Flask app whose generated downloads module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
  - Source Reference: `tests/deploy-canaries/flask-patterns`

### Success Checks
- App responds on its public URL: HTTP GET `/` expecting `ample canary flask patterns`
- Generated-downloads self-test: HTTP GET `/p/generated-downloads` expecting `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 Flask major versions are not verified.
- The recruiting tracker itself (your export formats, retention policy and entitlement model) 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.

### Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Basis**: size prices from pricing.toml
- **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

### Evidence Summary
- **Canary Run**: Flask pattern fixture deployed on Ample, checks passed for generated-downloads and configuration-secrets.
  - Observed At: 2026-09-21T01:14:18Z
- **Canary Run**: The same Flask app deployed with a --release-command migration; the marker it created was readable after activation.
  - Observed At: 2026-09-20T01:54:51Z

### Next Actions
- Browse the catalog index
- Search published recipes by intent, stack and constraints
- Prepare a side-effect-free deployment plan for an authorized project
- Read the existing agent authentication setup
- Browse Recruiting tracker
- Browse Flask
- Browse Generated downloads
- Browse Deploy web app
