page:recipes:client portal:django:public profiles

Host client portal with Django: public profile assets

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

Representative Queries

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. A bucket from ample bucket create with its credentials passed as encrypted S3_* environment variables and a second, published bucket for public assets (CDN_*)
  4. An Ample account token with servers:write, databases:read, buckets:read

Workflow Steps

1. Build and start

2. Implement the pattern on PostgreSQL

The fixture's module implements public image delivery: 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). 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.

5. Verify

Fetch the live URL and the pattern self-test route(s) (/p/public-media-library, /p/private-document-library) from the example; then run your own checks. On failure read ample logs --kind build then --kind runtime.

Cost Estimate

Limitations

Next Actions

  1. Browse the catalog index

    • Action ID: browse-catalog
    • Method: GET
    • Path: /v1/catalog

  2. Search published recipes by intent, stack and constraints

    • Action ID: search-recipes
    • Method: POST
    • Path: /v1/catalog/search

  3. Prepare a side-effect-free deployment plan for an authorized project

    • Action ID: plan:page:recipes:client-portal:django:public-profiles
    • Method: POST
    • Path: /v1/catalog/plan

  4. Read the existing agent authentication setup

    • Action ID: auth-setup
    • Method: GET
    • Path: /mcp/setup

  5. Browse Client portal

    • Action ID: browse:workload:client-portal
    • Method: GET
    • Path: /v1/catalog/nodes/workload%3Aclient-portal

  6. Browse Django

    • Action ID: browse:stack:framework-django
    • Method: GET
    • Path: /v1/catalog/nodes/stack%3Aframework-django

  7. Browse Public image delivery

    • Action ID: browse:pattern:public-image-delivery
    • Method: GET
    • Path: /v1/catalog/nodes/pattern%3Apublic-image-delivery

  8. Browse Deploy web app

    • Action ID: browse:intent:deploy-web-app
    • Method: GET
    • Path: /v1/catalog/nodes/intent%3Adeploy-web-app