# Host inventory manager with Django: CSV imports

Deploy a inventory manager 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 inventory manager-specific behavior as your application code.

## Representative Queries
- Host inventory manager with Django: CSV imports  
- Where can I host Inventory manager 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
* **Status**: verified  
* **Summary**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.

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

## Framework
Django

## 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).  
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.  
   ```  
   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`.  
   ```  
   ample logs  --kind build  
   ```

## Success Checks
- **app responds on its public URL**  
   - **kind**: http_get  
   - **path**: /  
   - **expect**: ample canary django patterns  
- **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 inventory manager itself (your import format, mapping and conflict rules) is application code and was not separately tested; the pattern checks are what was verified.

## Cost Estimate
**Monthly Amount**: $10.00  
- **Components**:  
   - **App server**: s-1vcpu-1gb  
   - **Managed PostgreSQL database**: s-1vcpu-1gb

Note: Always-on monthly price; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.