Nonprofits: event registration using Django · Ample Computer

Nonprofits: event registration using Django

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

Public information: mission and programs, events, donation entry point. Kept out of scope until handling is reviewed: beneficiary identity and case notes, donor records. Beneficiary and donor data are sensitive; donations are handled by your payment provider. 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

Steps

  1. Model the nonprofits domain. Create the tables course_groups, memberships, sessions, materials, events. Programs and cohorts lives in course_groups; keep the sensitive classes (beneficiary identity and case notes, donor 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=...
    
  7. Verify. Run the pattern self-test(s) from the example (/p/transactional-workflows) and your own acceptance checks for the nonprofits 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 Nonprofits schema and workflow below build on that verified basis.

Tested examples

What it doesn’t cover