Sports clubs: member portal using Django

Summary

A member portal blueprint for sports clubs built with Django on Ample. Domain schema:

• course_groups (team_or_class, season, age_group): teams and classes;
• memberships (course_group_id, member_reference, guardian_reference, role): players, guardians and coaches;
• sessions (course_group_id, starts_at, venue, type): training and fixtures;
• materials (course_group_id, title, object_key, visibility): schedules and coaching resources;
• document_access (document_id, principal_reference, role, granted_at): who may read which document.

Public information includes teams, seasons and fixtures, venues, and membership fees. Kept out of scope until handling is reviewed: minor members and medical notes, safeguarding records. Medical and safeguarding records are sensitive; only schedules and coaching materials 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).

Resource Requirements

• primitive:compute
• primitive:postgres
• primitive:s3-compatible-object-storage

Infrastructure Requirements

Framework

Django

Workload

Member portal

Industry

Sports clubs

Release Status

published

Support Status

verified

Execution Status

ready

Prerequisites

1. 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)
2. A PostgreSQL driver reading DATABASE_URL (auto-provisioned when omitted)
3. Bucket credentials from ample bucket create passed as encrypted S3_* environment variables
4. A review of which sports clubs data classes may be handled at all; this blueprint models public information only

Workflow Steps

1. Model the sports clubs domain
   Create the tables course_groups, memberships, sessions, materials, document_access. Teams and classes live in course_groups; keep the sensitive classes (minor members and medical notes, safeguarding 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.

7. Verify
   Run the pattern self-test(s) from the example (/p/private-document-library) and your own acceptance checks for the sports clubs workflow.

Examples

• Django pattern fixture: Verified private document library basis for this blueprint.

Success Checks

• App responds on its public URL (GET /): expect "ample canary django patterns".
• Private-document-library self-test from the example (GET /p/private-document-library): expect to see the pattern fixture checks.

Limitations

• The technical basis (private document library on Django) was verified with the pattern fixture; the sports clubs schema and workflow are an original design for this blueprint and were not executed as a separate application.
• No health, financial, privacy, or other compliance claim is made. Medical and safeguarding records are sensitive; only schedules and coaching materials are modeled.
• Public content and synthetic examples only until actual data-handling requirements have been reviewed.
• Verified on the python-3.12 template at s-1vcpu-1gb; region, request-duration limits, and other sizes are unknown or unverified.
• Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified.
• PutObject and GetObject with path-style addressing are verified; other S3 operations and CDN cache rules are not.

Cost Estimate

Components

1. App server: size s-1vcpu-1gb, quantity 1.0, monthly amount 5.0
2. Managed PostgreSQL database: size s-1vcpu-1gb, quantity 1.0, monthly amount 5.0

Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

Evidence Summary

• 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).

Last Verified At

2026-09-20T03:31:44Z

Unknowns

• Region availability is unknown until a verified region fact is recorded.
• Compliance attestations are unknown; none are claimed.

Formats

• HTML: Link
• Markdown: Link
• JSON: Link

Next Actions

• Browse the catalog index
• Search published recipes by intent, stack, and constraints.
• Prepare a side-effect-free deployment plan for an authorized project.