### Nonprofits: asset library using Django

A asset library blueprint for nonprofits built with Django on Ample. Domain schema:

- **course_groups** *(program, cohort, start_at, end_at)*: programs and cohorts;  
- **memberships** *(course_group_id, participant_reference, role)*: participants, volunteers and staff;  
- **sessions** *(course_group_id, starts_at, title, location)*: program sessions and events;  
- **materials** *(course_group_id, title, object_key, visibility)*: program materials;  
- **uploads** *(id, owner_reference, object_key, content_type, size, uploaded_at)*: validated uploads linked to their owner.

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 and are not modeled here. Technical basis verified on Django: content-type and size validation that rejects disallowed files, an object written to a private bucket and a row linking the record to the object key (reject=ok upload=ok linked=ok).

#### Representative Queries
- Nonprofits: asset library using Django
- Where can I host Nonprofits: Asset library built with Django?
- I need a genuinely specialized asset library workflow covering program participation, volunteer events and program resources.

#### Workflow Steps
1. **Model the nonprofits domain**: Create the tables course_groups, memberships, sessions, materials, uploads. 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 assets linked to their owning group or workspace.
3. **Workflow step 2**: Validate uploads and store them in the private bucket; link each object to its row.
4. **Workflow step 3**: Authorize downloads by membership.
5. **Workflow step 4**: Deploy and verify rejection of disallowed files and a linked upload.
6. **Deploy**: Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
   - Command: `ample deploy . --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/browser-file-uploads) and your own acceptance checks for the nonprofits workflow.
   - Command: `ample logs --kind build`

#### Technical Requirements
- **Framework**: Django  
- **Workload**: Asset library  
- **Industry**: Nonprofits  
- **Release Status**: published  
- **Support Status**: verified  
- **Execution Status**: ready  
- **Prerequisites**: 
  - 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)  
  - A PostgreSQL driver reading DATABASE_URL (auto-provisioned when omitted)  
  - Bucket credentials from `ample bucket create` passed as encrypted S3_* environment variables  
  - A review of which nonprofits data classes may be handled at all; this blueprint models public information only

#### Cost Estimate
- **Currency**: USD  
- **Monthly Amount**: 10.0  
- **Basis**: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty

##### Components
- App server: size s-1vcpu-1gb, quantity 1.0, monthly amount 5.0  
- 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.