### Host partner portal with Django: application activity history

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

#### Representative Queries
- Host partner portal with Django: application activity history
- Where can I host Partner portal built with Django?
- I need an application-owned event schema and tested history queries; not native platform audit logs.

#### Resource Requirements
- Compute
- Postgres

#### Infrastructure Requirements
1. **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.
2. **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.

#### 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)
- An Ample account token with servers:write, databases:read

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

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

#### Examples
- **Django pattern fixture**: Multi-pattern Django app whose transactional workflows module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

#### Success Checks
1. App responds on its public URL
2. Transactional-workflows self-test

#### 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 partner portal itself (your domain records, validation rules and concurrency policy) is application code and was not separately tested; the pattern checks are what was verified.

#### Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **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

#### Evidence Summary
- Checks passed for transactional-workflows and configuration-secrets.