Host knowledge base with Django: object-stored public media

Deploy a knowledge base built with Django on Ample using the public media library 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: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly. Not separately tested: your media processing, object layout and cache policy; treat the knowledge base-specific behavior as your application code.

Representative Queries

• Host knowledge base with Django: object-stored public media
• Where can I host Knowledge base built with Django?
• I need an object layout, public asset URL policy and CDN delivery configuration.

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 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. S3-compatible object storage
   Buckets are S3-compatible with issued credentials; PutObject and GetObject are 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.

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).
• A bucket from ample bucket create with its credentials passed as encrypted S3_* environment variables and a second, published bucket for public assets (CDN_*).
• An Ample account token with servers:write, databases:read, buckets: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 public media library: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly. 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.
   Command: 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/public-media-library) from the example; then run your own checks. On failure read ample logs --kind build then --kind runtime.
   Command: ample logs --kind build

Success Checks

• App responds on its public URL (Expect: ample canary django patterns)
• Public-media-library self-test (Expect: a CDN URL whose content is served publicly)

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 knowledge base itself (your media processing, object layout and cache policy) is application code and was not separately tested; the pattern checks are what was verified.

Cost Estimate

• Monthly Amount: 10.0 USD
• Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
• Components:
  1. App server: size s-1vcpu-1gb, quantity 1.0, monthly amount 5.0
  2. Managed PostgreSQL database: size s-1vcpu-1gb, quantity 1.0, monthly amount 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.

Evidence Summary

• Canary Run: Django pattern fixture deployed on Ample (checks passed for public-media-library and configuration-secrets).
• Last Verified At: 2026-09-20T03:31:44Z

Next Actions

1. Browse the catalog index
   Method: GET, Relative Path: /v1/catalog
   Requires Authentication: No
2. Search published recipes by intent, stack and constraints
   Method: POST, Relative Path: /v1/catalog/search
   Requires Authentication: No
   Parameters: { "body": { "limit": 5, "query": "Host knowledge base with Django: object-stored public media" }}
3. Prepare a side-effect-free deployment plan for an authorized project
   Method: POST, Relative Path: /v1/catalog/plan
   Requires Authentication: Yes
   Parameters: { "body": { "inputs": {}, "projectId": "", "recipeId": "page:recipes:knowledge-base:django:public-media", "recipeRevision": "r1" }}