# Host community forum with Django: application activity history

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

## Representative Queries
- Host community forum with Django: application activity history
- Where can I host Community forum 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
- **Compute**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
- **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
Community forum

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

## Input Schema
- **Name**: App name (required, max length: 63, pattern: ^[a-z0-9-]+$)
- **Path**: Project directory or ample.toml service (required, max length: 512)
- **Start**: Start command (required, max length: 512)
- **Env**: Encrypted environment variables (optional, max items: 50)
- **Release Command**: Migration command run before activation (optional, max length: 512)

## 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...
3. **Deploy**: Run the synchronous deploy once and read the result...
4. **Verify**: Fetch the live URL and the pattern self-test route(s)....

## 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
- App responds on its public URL.
- 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 community forum itself (your domain records...) is application code and was not separately tested.

## Cost Estimate
- **Monthly Amount**: $10.00
- **Components**: App server, managed PostgreSQL database.
- **Note**: Always-on monthly price of the tested sizes...

## Evidence Summary
- **Canary Run**: Django pattern fixture deployed on Ample...

## Last Verified At
2026-09-20T03:31:44Z

## Unknowns
- Region availability is unknown until a verified region fact is recorded.

## Formats
- [HTML Format](/content/recipes/community-forum/django/activity-history/index.html)
- [Markdown Format](/content/recipes/community-forum/django/activity-history.md)
- [JSON Format](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Acommunity-forum%3Adjango%3Aactivity-history)