Membership associations: event registration using Django · Ample Computer

Membership associations: event registration using Django

An event registration blueprint for membership associations built with Django on Ample. Domain schema:

Public information: about, chapters and benefits, public events, join information. Kept out of scope until handling is reviewed: member directory details, dues and payment records. Member directories are personal data; only public events and member-authorized resources are modeled. 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

install

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

runtime

python

sizes-1vcpu-1gb

start

PYTHONPATH=.ample/python:${PYTHONPATH:-} python3 run.py

template python-3.12

Steps

  1. Model the membership associations domain. Create the tables course_groups, memberships, sessions, materials, events. Chapters and programs as groups live in course_groups; keep the sensitive classes (member directory details, dues and payment records) 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 membership associations workflow.
$ ample logs <deployment_id> --kind build

How it was checked

✓ app responds on its public URL · http get/ → “ample canary django patterns”
✓ transactional-workflows self-test from the example · http get/p/transactional-workflows → “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 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 Membership associations schema and workflow below build on that verified basis.

Tested examples

What it doesn’t cover