Course creators: event registration using Django · Ample Computer

Course creators: event registration using Django

An event registration 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; events (seq, record_type, record_id, kind, at): application-owned history written in the same transaction. 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: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected).

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 course creators domain. Create the tables course_groups, memberships, sessions, materials, events. Cohorts as course groups lives in course_groups; keep the sensitive classes (learner progress and grades, recordings showing learners, payment status) out of this schema.

  2. Workflow step 1. Model sessions with capacity and registrations with status

  3. Workflow step 2. Register transactionally with a capacity check and an event per registration

  4. Workflow step 3. Reject stale concurrent updates

  5. Workflow step 4. Deploy and verify history and conflict handling

  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/transactional-workflows) and your own acceptance checks for the course creators workflow.
$ ample logs <deployment_id> --kind build

How it was checked

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 transactional workflows checks passed: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). The blueprint's Course creators schema and workflow below build on that verified basis.

Tested examples

What it doesn’t cover