Video production: asset library using Django · Ample Computer

Video production: asset library using Django

An asset library blueprint for video production built with Django on Ample. Domain schema:
customer_workspaces (client_name, project_count): client organizations;
projects (workspace_id, title, stage, delivery_due_at): productions in flight;
cuts (project_id, version, object_key, review_status, reviewed_at): versioned cuts for review;
customer_assets (workspace_id, project_id, object_key, visibility): final deliverables and raw footage access;
uploads (id, owner_reference, object_key, content_type, size, uploaded_at): validated uploads linked to their owner. Public information: showreel and services, production process, contact. Kept out of scope until handling is reviewed: unreleased footage, talent releases and contracts, client brand material. Footage is large and confidential; upload large files straight to the bucket with ample bucket upload-url. 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

install python3 -m pip install --target .ample/python -r requirements.txt

runtime:
sizes: 1vcpu-1gb
start: PYTHONPATH=.ample/python:${PYTHONPATH:-} python3 run.py
template: python-3.12

Steps

  1. Model the video production domain. Create the tables customer_workspaces, projects, cuts, customer_assets, uploads. Client organizations lives in customer_workspaces; keep the sensitive classes (unreleased footage, talent releases and contracts, client brand material) out of this schema.

  2. Workflow step 1. Model assets linked to their owning group or workspace

  3. Workflow step 2. Validate uploads and store them in the private bucket; link each object to its row

  4. Workflow step 3. Authorize downloads by membership

  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=...
    
  7. Verify. Run the pattern self-test(s) from the example (/p/browser-file-uploads) and your own acceptance checks for the video production 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 Video production schema and workflow below build on that verified basis.

Tested examples

What it doesn’t cover