# Host csv import tool with Django: relational workflow state

Deploy a csv import tool built with Django on Ample using the transactional workflows 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: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). Not separately tested: your domain records, validation rules and concurrency policy; treat the csv import tool-specific behavior as your application code.

## Representative Queries
- Host csv import tool with Django: relational workflow state
- Where can I host CSV import tool built with Django?
- I need a domain record schema, validation rules and concurrency behavior.

## Resource Requirements
- Compute
- Postgres

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

## Framework
Django

## Workload
CSV import tool

## Release Status
published

## Support Status
verified

## Execution Status
ready

## Prerequisites
1. 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)
2. A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)
3. 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

## Input Schema
- **name**: App name (1–63 characters, pattern: ^[a-z0-9-]+$).
- **path**: Project directory or ample.toml service (1–512 characters).
- **start**: Start command (1–512 characters).
- **release_command**: Migration command run before activation (up to 512 characters).
- **env**: Encrypted environment variables (up to 50 items, pattern: ^[A-Z][A-Z0-9_]*=.*$).

## 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**: The fixture's module implements transactional workflows: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). 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/transactional-workflows) from the example; then run your own checks. On failure read `ample logs  --kind build` then `--kind runtime`.
   Command: ample logs  --kind build

## 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 csv import tool itself (your domain records, validation rules and concurrency policy) 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
- **Basis**: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty.
- **Components**:
  - **App Server**: s-1vcpu-1gb, quantity: 1.0, monthly amount: 5.0
  - **Managed PostgreSQL Database**: s-1vcpu-1gb, quantity: 1.0, monthly amount: 5.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.

## Success Checks
1. **App responds on its public URL**: (kind: http_get, path: /, expect: ample canary django patterns)
2. **Transactional-workflows self-test**: (kind: http_get, path: /p/transactional-workflows, expect: tx=ok history=2 conflict=rejected)

## Next Actions
- **Browse the catalog index**: (GET /v1/catalog)
- **Search recipes by intent**: (POST /v1/catalog/search)
- **Prepare a deployment plan**: (POST /v1/catalog/plan)
- **Read the existing agent authentication setup**: (GET /mcp/setup)
- **Browse CSV import tool**: (GET /v1/catalog/nodes/workload%3Acsv-import-tool)
- **Browse Django**: (GET /v1/catalog/nodes/stack%3Aframework-django)
- **Browse Transactional workflows**: (GET /v1/catalog/nodes/pattern%3Atransactional-workflows)
- **Browse Deploy web app**: (GET /v1/catalog/nodes/intent%3Adeploy-web-app)