page:recipes:public directory:django:content imports

Host public directory with Django: bulk content imports

Deploy a public directory built with Django on Ample using the bulk import staging 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. Verified on Django: a CSV staged as an object, row-level validation with per-row errors recorded, and a restart-safe import keyed by import id (imported=2 rejected=1 restart=ok). Not separately tested: your import format, mapping and conflict rules; treat the public directory-specific behavior as your application code.

Representative Queries

• Host public directory with Django: bulk content imports
• Where can I host Public directory built with Django?
• I need a staged import format, validation procedure and import recovery workflow.

Resource Requirements

• primitive:compute
• primitive:postgres
• primitive:s3-compatible-object-storage

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.
• S3-compatible object storage: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

Framework

Django

Workload

Public directory

Release Status

published

Support Status

verified

Execution Status

ready

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
• 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 bulk import staging: a CSV staged as an object, row-level validation with per-row errors recorded, and a restart-safe import keyed by import id (imported=2 rejected=1 restart=ok). 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.

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=...

5. Verify: Fetch the live URL and the pattern self-test route(s) (/p/bulk-import-staging) from the example; then run your own checks. On failure read ample logs --kind build then --kind runtime.

   Command: ample logs --kind build

Examples

• Django pattern fixture: Multi-pattern Django app whose bulk import staging module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

Success Checks

• App responds on its public URL: Expect ample canary django patterns.
• Bulk-import-staging self-test: Expect imported=2 rejected=1 restart=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 public directory itself (your import format, mapping and conflict rules) 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.
• PutObject and GetObject with path-style addressing are verified; multipart upload, listing, presigned URLs and lifecycle rules are not verified.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Authoritative: true
• 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, monthlyAmount: 5.0)
• Managed PostgreSQL database (size: 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.

Evidence Summary

1. Canary run: Django pattern fixture deployed on Ample (pip install into .ample/python from requirements.txt, then waitress serving project.wsgi from run.py reading PORT on the python-3.12 template); checks passed for bulk-import-staging and configuration-secrets. Pattern proof: a CSV staged as an object, row-level validation with per-row errors recorded, and a restart-safe import keyed by import id (imported=2 rejected=1 restart=ok).
   • Observed At: 2026-09-20T03:31:44Z
   • Implementation Revision: 03b6402b1b3e19178985f08ea4033804521d85d4-dirty (CLI b75e104)
   • Expires At: 2027-03-19T03:31:44Z
2. Canary run: The same Django app deployed with a --release-command migration; the marker it created was readable after activation.
   • Observed At: 2026-09-20T01:54:51Z
   • Implementation Revision: 199ff1dfd52683832ae75d3f98b53a7a4bff7f96-dirty (CLI e3181f5)
   • Expires At: 2027-03-19T01:54:51Z

Unknowns

• Region availability is unknown until a verified region fact is recorded.
• Compliance attestations are unknown; none are claimed.

Formats

• HTML Format
• Markdown Format
• JSON Format

Next Actions

• Browse the catalog index: GET /v1/catalog
• Search published recipes by intent, stack and constraints: POST /v1/catalog/search (Body: {"limit":5,"query":"Host public directory with Django: bulk content imports"})
• Prepare a side-effect-free deployment plan for an authorized project: POST /v1/catalog/plan (Body: {"inputs":{},"projectId":"","recipeId":"page:recipes:public-directory:django:content-imports","recipeRevision":"r1"})
• Read the existing agent authentication setup: GET /mcp/setup
• Browse Public directory: GET /v1/catalog/nodes/workload%3Apublic-directory
• Browse Django: GET /v1/catalog/nodes/stack%3Aframework-django
• Browse Bulk import staging: GET /v1/catalog/nodes/pattern%3Abulk-import-staging
• Browse Deploy web app: GET /v1/catalog/nodes/intent%3Adeploy-web-app