# Host partner portal with Django: tenant-scoped workspaces

Deploy a partner portal built with Django on Ample using the multi-tenant relational data 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: a tenant column on every row and query, with a cross-tenant read returning nothing (tenant_isolation=ok). Not separately tested: your tenant model, membership and per-tenant authorization; treat the partner portal-specific behavior as your application code.

## Representative Queries
- Host partner portal with Django: tenant-scoped workspaces
- Where can I host Partner portal built with Django?
- I need an explicit tenant model and application-enforced tenant isolation tests.

## Resource Requirements
- primitive:compute
- primitive:postgres

## Infrastructure Requirements
1. **Compute**  
   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**  
   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
Partner portal

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

### 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 multi-tenant relational data: a tenant column on every row and query, with a cross-tenant read returning nothing (tenant_isolation=ok). 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.
   ```bash
   ample deploy . --name  --public --start "python3 run.py"
   ```
4. **Verify**  
   Fetch the live URL and the pattern self-test route(s) (/p/multi-tenant-relational-data) from the example; then run your own checks. On failure read `ample logs  --kind build` then `--kind runtime`.
   ```bash
   ample logs  --kind build
   ```

### Examples
- **Django pattern fixture**  
  Multi-pattern Django app whose multi-tenant relational data module was checked live; the module is under tests/deploy-canaries/_pattern-modules.  
  Source: tests/deploy-canaries/django-patterns

### Success Checks
1. app responds on its public URL  
   - **Kind**: http_get  
   - **Path**: /  
   - **Expect**: ample canary django patterns
2. multi-tenant-relational-data self-test  
   - **Kind**: http_get  
   - **Path**: /p/multi-tenant-relational-data  
   - **Expect**: tenant_isolation=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 partner portal itself (your tenant model, membership and per-tenant authorization) 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  
  - Cost breakdown:  
    - app server: s-1vcpu-1gb (quantity: 1.0, monthlyAmount: 5.0)  
    - managed PostgreSQL database: s-1vcpu-1gb (quantity: 1.0, monthlyAmount: 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.