# Host vendor portal with Django: application activity history

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

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

## Resource Requirements
- primitive:compute
- primitive: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.  
   [More info](/discover/primitive/compute)

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.  
   [More info](/discover/primitive/postgres)

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

## Success Checks
1. App responds on its public URL  
   - **Check**: `http_get`  
   - **Path**: `/`  
   - **Expect**: ample canary django patterns

2. Transactional-workflows self-test  
   - **Check**: `http_get`  
   - **Path**: `/p/transactional-workflows`  
   - **Expect**: tx=ok history=2 conflict=rejected

## Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
   - **Authoritative**: true
   - **Basis**: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty  
   - **Components**:  
      - App server (s-1vcpu-1gb): $5.00/month  
      - Managed PostgreSQL database (s-1vcpu-1gb): $5.00/month  
      - **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.

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

## Next Actions
- **[Browse the catalog index](/v1/catalog)**
- **[Search published recipes by intent, stack and constraints](/v1/catalog/search)**
- **[Prepare a side-effect-free deployment plan for an authorized project](/v1/catalog/plan)**
- **[Read the existing agent authentication setup](/mcp/setup)**
- **[Browse Vendor portal](/v1/catalog/nodes/workload%3Avendor-portal)**
- **[Browse Django](/v1/catalog/nodes/stack%3Aframework-django)**
- **[Browse Transactional workflows](/v1/catalog/nodes/pattern%3Atransactional-workflows)**
- **[Browse Deploy web app](/v1/catalog/nodes/intent%3Adeploy-web-app)**