Course creators: member portal using Django · Ample Computer
Course creators: member portal using Django
A member portal blueprint for course creators built with Django on Ample. Domain schema:
- course_groups (name, start_at, end_at, capacity): cohorts as course groups;
- memberships (course_group_id, member_email, role, joined_at): learner and instructor membership;
- sessions (course_group_id, starts_at, title, recording_object_key): session events and recordings;
- materials (course_group_id, title, object_key, visibility): teaching materials;
- document_access (document_id, principal_reference, role, granted_at): who may read which document.
Public information: course catalog and syllabus, instructor profile, schedule. Kept out of scope until handling is reviewed: learner progress and grades, recordings showing learners, payment status. Recordings and progress data are personal data; materials are authorized per course group. Technical basis verified on Django: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok).
What it runs on
Computeverified
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.Postgresverified
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 storageverified
Buckets speak the S3 API with SigV4 credentials Ample Computer issues;ample bucket upload-urlreturns 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 createpassed as encrypted S3_* environment variables - A review of which course creators data classes may be handled at all; this blueprint models public information only
Exact tested configuration
python3 -m pip install --target .ample/python -r requirements.txtpython- sizes-1vcpu-1gb
PYTHONPATH=.ample/python:${PYTHONPATH:-} python3 run.py- templatepython-3.12
Steps
Model the course creators domain. Create the tables course_groups, memberships, sessions, materials, document_access. Cohorts as course groups live in course_groups; keep the sensitive classes (learner progress and grades, recordings showing learners, payment status) out of this schema.
Workflow step 1. Model groups, memberships and roles
Workflow step 2. Authorize access to materials by membership and role (401, 403 negative tests)
Workflow step 3. Store materials in the private bucket and stream them through the app
Workflow step 4. Deploy and verify the negative tests and an authorized download
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=...Verify. Run the pattern self-test(s) from the example (/p/private-document-library) and your own acceptance checks for the course creators workflow.
$ ample logs <deployment_id> --kind build
How it was checked
✓ app responds on its public URL· http get/ → “ample canary django patterns”
✓ private-document-library self-test from the example· http get/p/private-document-library → “see the pattern fixture checks”
Evidence
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 private document library checks passed: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok). The blueprint's Course creators schema and workflow below build on that verified basis.
Tested examples
- Django pattern fixture. Verified private document library basis for this blueprint.
What it doesn’t cover
- The technical basis (private document library on Django) was verified with the pattern fixture; the course creators schema and workflow are an original design for this blueprint, built on that basis.
- Recordings and progress data are personal data; materials are authorized per course group.
- 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-urlreturns presigned upload URLs.