Membership associations: member portal using Django · Ample Computer

Membership associations: member portal using Django

A member portal blueprint for membership associations built with Django on Ample. Domain schema: course_groups (chapter_or_program, start_at, end_at): chapters and programs as groups; memberships (course_group_id, member_email, tier, role, renewed_at): members and roles; sessions (course_group_id, starts_at, title, venue): meetings and events; materials (course_group_id, title, object_key, visibility): member resources; document_access (document_id, principal_reference, role, granted_at): who may read which document. 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: 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

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 membership associations domain. Create the tables course_groups, memberships, sessions, materials, document_access. 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 groups, memberships and roles
  3. Workflow step 2. Authorize access to materials by membership and role (401, 403 negative tests)
  4. Workflow step 3. Store materials in the private bucket and stream them through the app
  5. Workflow step 4. Deploy and verify the negative tests and an authorized download
  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/private-document-library) 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”
✓private-document-library self-test from the example· http get/p/private-document-library → “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 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 Membership associations schema and workflow below build on that verified basis.

Tested examples

What it doesn’t cover