# 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
- **[Compute](/content/discover/primitive/compute/index.html)**  
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.
- **[Postgres](/content/discover/primitive/postgres/index.html)**  
Managed PostgreSQL 16 with pgvector 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](/content/discover/primitive/s3-compatible-object-storage/index.html)**  
Buckets speak the S3 API with SigV4 credentials Ample Computer issues; `ample bucket upload-url` returns a presigned upload URL. PutObject and GetObject are checked by canary.

## You need
- A Django project (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 (auto-provisioned when omitted)
- Bucket credentials from `ample bucket create` passed as encrypted S3_* environment variables
- A review of which video production data classes may be handled at all; this blueprint models public information only

## 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
- **Django pattern fixture.** Verified browser file uploads basis for this blueprint.

## What it doesn’t cover
- The technical basis (browser file uploads on Django) was verified with the pattern fixture; the video production schema and workflow are an original design for this blueprint, built on that basis.
- Footage is large and confidential; upload large files straight to the bucket with `ample bucket upload-url`.
- Verified on the python-3.12 template at s-1vcpu-1gb.
- Managed PostgreSQL 16 with pgvector.
- Buckets speak the standard S3 API (PutObject and GetObject with path-style addressing are checked by the fixture); `ample bucket upload-url` returns presigned upload URLs.
