page:recipes:blog:django:relational content

Host blog with Django: Postgres-backed content

Deploy a blog built with Django on Ample using the relational records 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, and a published bucket serves public assets from the CDN host. Verified on Django: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). Not separately tested: your record schema, states and access rules; treat the blog-specific behavior as your application code.

Representative Queries

• Host blog with Django: Postgres-backed content
• Where can I host Blog built with Django?
• I need a content schema, publishing workflow and cache behavior after content updates.

Resource Requirements

• primitive:compute
• primitive:postgres
• 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 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.

3. 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 relational records: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). Copy the approach into your schema; 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. Keep private data in an unpublished bucket. Publish only the bucket that serves public assets and reference its CDN URL.

4. 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.
   ample deploy . --name --public --start "python3 run.py" --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=... --env CDN_PUBLIC_URL=...

5. Verify
   Fetch the live URL and the pattern self-test route(s) (/p/relational-records) from the example; then run your own checks. On failure read ample logs --kind build then --kind runtime.
   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 blog itself (your record schema, states and access rules) is application code and was not separately tested; the pattern checks are what was verified.

Cost Estimate

• Currency: USD
• Monthly Amount: $10.00
• Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
• Components:
  • App server
    • Size: s-1vcpu-1gb
    • Quantity: 1.0
    • Monthly Amount: $5.00
  • Managed PostgreSQL database
    • Size: s-1vcpu-1gb
    • Quantity: 1.0
    • Monthly Amount: $5.00

Examples

• Django pattern fixture
  Multi-pattern Django app whose relational records module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
  • sourceRef: tests/deploy-canaries/django-patterns

Success Checks

1. app responds on its public URL

   • kind: http_get
   • path: /
   • expect: ample canary django patterns

2. relational-records self-test

   • kind: http_get
   • path: /p/relational-records
   • expect: records=ok transitions=true isolation=true

Evidence Summary

• Django pattern fixture deployed on Ample...
• The same Django app deployed with a --release-command migration...