### Host vendor portal with Django: public profile assets

Deploy a vendor portal built with Django on Ample using the public image delivery 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, and a published bucket serves public assets from the CDN host. Verified on Django: public objects in a published bucket served from the CDN URL, kept separate from private objects in an unpublished bucket that require authorization (private=ok only for the allowed role). Not separately tested: your image processing and profile-media rules; treat the vendor portal-specific behavior as your application code.

#### Representative Queries
- Host vendor portal with Django: public profile assets
- Where can I host Vendor portal built with Django?
- I need separate public profile media from private data, with CDN cache rules.

#### Resource Requirements
- primitive:compute
- primitive:postgres
- primitive:s3-compatible-object-storage
- primitive:cdn

#### Infrastructure Requirements
1. **Compute**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are 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.
3. **S3-compatible object storage**: Buckets are S3-compatible with issued credentials; verified by canary. Other S3 operations are not verified.
4. **CDN**: The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.

### 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 public image delivery; 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.
4. **Deploy**: Run the synchronous deploy once and read the result.
5. **Verify**: Fetch the live URL and the pattern self-test route(s) from the example; then run your own checks.

#### Examples
- **Django pattern fixture**: Multi-pattern Django app whose public image delivery module was checked live.

#### Limitations
- Verified only on the python-3.12 template at s-1vcpu-1gb with the example fixture; other sizes and Django major versions are not verified.

#### Cost Estimate
- **Currency**: USD 
- **Monthly Amount**: 10.0 
- **Components**: 
  - *app server*: s-1vcpu-1gb 
  - *managed PostgreSQL database*: s-1vcpu-1gb

#### Next Actions
- [Browse the catalog index](https://api.ample.computer/v1/catalog)
- [Prepare a side-effect-free deployment plan](https://api.ample.computer/v1/catalog/plan)
- [Browse Vendor portal](https://api.ample.computer/v1/catalog/nodes/workload%3Avendor-portal)