Digital agencies: form collection using Django · Ample Computer

Digital agencies: form collection using Django

A form collection blueprint for digital agencies built with Django on Ample. Domain schema:
client_entities (name, brand, primary_contact_role): client brands;
engagements (client_entity_id, campaign_or_project, period_start, period_end, status): retainers and projects;
approval_rounds (engagement_id, round_no, asset_object_key, status, decided_at): creative approval rounds;
deliverables (engagement_id, title, object_key, version): final assets delivered;
uploads (id, owner_reference, object_key, content_type, size, uploaded_at): validated uploads linked to their owner.
Public information: services and case studies, team, contact.
Kept out of scope until handling is reviewed: unreleased creative and campaign plans, client analytics exports, brand credentials.
Unreleased creative is confidential; brand platform credentials never belong in these flows.
Technical basis verified on Django: content-type and size validation that rejects disallowed files, an object written to a private bucket and a row linking the record to the object key (reject=ok upload=ok linked=ok).

What it runs on

You need

Exact tested configuration

installpython3 -m pip install --target .ample/python -r requirements.txt
runtimepython sizes-1vcpu-1gb startPYTHONPATH=.ample/python:${PYTHONPATH:-} python3 run.py templatepython-3.12

Steps

  1. Model the digital agencies domain. Create the tables client_entities, engagements, approval_rounds, deliverables, uploads. Client brands lives in client_entities; keep the sensitive classes (unreleased creative and campaign plans, client analytics exports, brand credentials) out of this schema.
  2. Workflow step 1. Model document requests per engagement with due dates and status
  3. Workflow step 2. Validate uploaded files (type, size) before storing them in the private bucket and linking them to the request
  4. Workflow step 3. Authorize uploads by client entity
  5. Workflow step 4. Deploy and verify rejection of disallowed files and a linked upload
  6. Deploy. Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
   $ ample deploy . --name <app-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=...
  1. Verify. Run the pattern self-test(s) from the example (/p/browser-file-uploads) and your own acceptance checks for the digital agencies workflow.
   $ ample logs <deployment_id> --kind build

How it was checked

✓ app responds on its public URL · http get/ → “ample canary django patterns”
✓ browser-file-uploads self-test from the example · http get/p/browser-file-uploads → “see the pattern fixture checks”

Evidence

  1. November 6, 2026 · 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); the browser file uploads checks passed: content-type and size validation that rejects disallowed files, an object written to a private bucket and a row linking the record to the object key (reject=ok upload=ok linked=ok). The blueprint's Digital agencies schema and workflow below build on that verified basis.

Tested examples

What it doesn’t cover