# Host help desk with Django: CSV imports

Deploy a help desk built with Django 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 Django: 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 help desk-specific behavior as your application code.

## Representative Queries
- Host help desk with Django: CSV imports
- Where can I host Help desk built with Django?
- I need a domain CSV format, row validation, deduplication and an import recovery path.

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

## Workload
Help desk

## Release Status
Published

## Support Status
Verified

## Execution Status
Ready

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

## 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
- env: Encrypted environment variables (bucket credentials, secrets)
- name: App name
- path: Project directory or ample.toml service
- release_command: Migration command run before activation
- start: Start command (Python apps pass one explicitly)

## 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 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
### Django pattern fixture
- **Description**: Multi-pattern Django app whose bulk import staging module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
- **Source Reference**: tests/deploy-canaries/django-patterns

## Success Checks
1. **app responds on its public URL**  
   - Kind: http_get  
   - Path: /  
   - Expect: ample canary django patterns
2. **bulk-import-staging self-test**  
   - Kind: http_get  
   - Path: /p/bulk-import-staging  
   - Expect: imported=2 rejected=1 restart=ok

## 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 help desk itself (your import format, mapping and conflict 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.
- PutObject and GetObject with path-style addressing are verified; multipart upload, listing, presigned URLs and lifecycle rules are not verified.

## Cost Estimate
- Currency: USD
- Monthly Amount: 10.0
- Authority: true
- Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
- 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
- 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.

## Evidence Summary
1. **Canary Run**  
   - Summary: Django pattern fixture deployed on Ample; checks passed for bulk-import-staging and configuration-secrets.
   - Observed At: 2026-09-20T03:31:44Z
   - Scope: checks: [ /p/bulk-import-staging ], pattern: pattern:bulk-import-staging, template: python-3.12
2. **Canary Run**  
   - Summary: The same Django app deployed with a --release-command migration; the marker it created was readable after activation.
   - Observed At: 2026-09-20T01:54:51Z
   - Scope: pattern: pattern:bulk-import-staging

## Last Verified At
2026-09-20T03:31:44Z

## Next Actions
1. **Browse the catalog index**  
   - Operation Id: catalog_index  
   - Method: GET  
   - Relative Path: /v1/catalog
2. **Search published recipes by intent, stack and constraints**  
   - Operation Id: search_recipes  
   - Method: POST  
   - Relative Path: /v1/catalog/search
3. **Prepare a side-effect-free deployment plan for an authorized project**  
   - Operation Id: plan_deployment  
   - Method: POST  
   - Relative Path: /v1/catalog/plan
4. **Read the existing agent authentication setup**  
   - Operation Id: existing_auth_setup  
   - Method: GET  
   - Relative Path: /mcp/setup
5. **Browse Help desk**  
   - Operation Id: browse_node  
   - Method: GET  
   - Relative Path: /v1/catalog/nodes/workload%3Ahelp-desk
6. **Browse Django**  
   - Operation Id: browse_node  
   - Method: GET  
   - Relative Path: /v1/catalog/nodes/stack%3Aframework-django
7. **Browse Bulk import staging**  
   - Operation Id: browse_node  
   - Method: GET  
   - Relative Path: /v1/catalog/nodes/pattern%3Abulk-import-staging
8. **Browse Deploy web app**  
   - Operation Id: browse_node  
   - Method: GET  
   - Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app