page:recipes:project tracker:fastapi:csv imports

Host project tracker with FastAPI: CSV imports

Summary

Deploy a project tracker built with FastAPI on Ample using the bulk import staging 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: a CSV staged as an object, row-level validation with per-row errors recorded, and a restart-safe import keyed by import id (imported=2 rejected=1 restart=ok). Not separately tested: your import format, mapping and conflict rules; treat the project tracker-specific behavior as your application code.

Framework

FastAPI

Workload

Project tracker

Release Status

Published

Support Status

Verified

Execution Status

Ready

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)
• A bucket from ample bucket create with its credentials passed as encrypted S3_* environment variables
• An Ample account token with servers:write, databases:read, buckets:read

Input Schema

• env: Encrypted environment variables (bucket credentials, secrets)
• name: App name (maxLength: 63, minLength: 1)
• path: Project directory or ample.toml service (maxLength: 512, minLength: 1)
• release_command: Migration command run before activation (maxLength: 512)
• start: Start command (maxLength: 512)

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 bulk import staging: a CSV staged as an object, row-level validation with per-row errors recorded, and a restart-safe import keyed by import id (imported=2 rejected=1 restart=ok). 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. Use path-style addressing. Keep private data in an unpublished bucket.
4. 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" --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...
5. Verify
   • Fetch the live URL and the pattern self-test route(s) (/p/bulk-import-staging) from the example; then run your own checks. On failure read ample logs --kind build then --kind runtime.
   • Command: ample logs --kind build

Examples

• FastAPI pattern fixture: Multi-pattern FastAPI app whose bulk import staging module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

Success Checks

• App responds on its public URL
• Bulk-import-staging self-test

Limitations

• Verified only on the python-3.12 template at s-1vcpu-1gb. Other sizes, templates and FastAPI major versions not verified.
• The project tracker itself (your import format, mapping and conflict rules) is application code and was not separately tested.

Cost Estimate

• Monthly Amount: $10.00 (USD)
• Components:
  • App server size: s-1vcpu-1gb - $5.00
  • Managed PostgreSQL database size: s-1vcpu-1gb - $5.00

Evidence Summary

• Canaries and proper self-test routes validated the bulk import staging.

Unknowns

• Region availability is unknown until a verified region fact is recorded.