## The short version

A member portal blueprint for tutoring centers built with Django on Ample. Domain schema:  
course_groups (subject, level, start_at, end_at, capacity): tutoring groups;  
 memberships (course_group_id, student_reference, guardian_reference, role): students, guardians and tutors;  
 sessions (course_group_id, starts_at, tutor, attendance_count): session events;  
 materials (course_group_id, title, object_key, visibility): worksheets and answer keys;  
 document_access (document_id, principal_reference, role, granted_at): who may read which document. Public information: subjects and levels, schedule and locations, tutor qualifications. Kept out of scope until handling is reviewed: minor students and guardian identity, progress reports. Data about minors is sensitive; only group schedules and materials are modeled here. 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 needs

- [Compute](/content/discover/primitive/compute/index.html): verified (Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.)  
- [Postgres](/content/discover/primitive/postgres/index.html): verified (Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.)  
- [S3-compatible object storage](/content/discover/primitive/s3-compatible-object-storage/index.html): verified (Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.)

## Before you start

- 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 tutoring centers data classes may be handled at all; this blueprint models public information only

## How to do it

1.  
### Model the tutoring centers domain  
Create the tables course_groups, memberships, sessions, materials, document_access. Tutoring groups lives in course_groups; keep the sensitive classes (minor students and guardian identity, progress reports) 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=...
```

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

```
ample logs <deployment_id> --kind build
```

## Tested examples

- **Django pattern fixture** (`tests/deploy-canaries/django-patterns`): Verified private document library basis for this blueprint.

## How to know it worked

- app responds on its public URL (`/` on the live URL, expect ample canary django patterns)  
- private-document-library self-test from the example (`/p/private-document-library` on the live URL, expect see the pattern fixture checks)

## Cost estimate

Estimated 10.00 USD per month (size prices from pricing.toml at build revision ca0b484a7a9957c573a88d3a32dc603c3c10135a).

- app server x1 `s-1vcpu-1gb`: 5.00 USD  
- managed PostgreSQL database x1 `s-1vcpu-1gb`: 5.00 USD

Upper-bound monthly price of the tested sizes. Buckets are allocation-priced per quota and not included.

## Verification evidence

- canary_run on 2026-09-20T03:31:44Z at revision `03b6402b1b3e19178985f08ea4033804521d85d4 (CLI b75e104)`: 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 Tutoring centers schema and workflow below build on that verified basis and were not separately executed. (expires 2027-03-19T03:31:44Z)

## Execution binding

MCP tool `ample_deploy` (registry `mcp:ample_deploy`), schema hash `876465fce906da0c` observed 2026-09-22T00:31:22.774679+00:00 at revision `e6446ceea69b`. Binding state at export: schema_changed. Required scopes: servers:write, databases:read, buckets:read.

## Typed next actions

- Browse the catalog index (`GET /v1/catalog` on the api origin; authentication not required, approval not required)  
- Search published recipes by intent, stack and constraints (`POST /v1/catalog/search` on the api origin; authentication not required, approval not required)  
- Prepare a side-effect-free deployment plan for an authorized project (`POST /v1/catalog/plan` on the api origin; authentication required, approval not required)  
- Read the existing agent authentication setup (`GET /mcp/setup` on the api origin; authentication not required, approval not required)  
- Browse Tutoring centers (`GET /v1/catalog/nodes/industry%3Atutoring-centers` on the api origin; authentication not required, approval not required)  
- Browse Member portal (`GET /v1/catalog/nodes/workload%3Amember-portal` on the api origin; authentication not required, approval not required)  
- Browse Django (`GET /v1/catalog/nodes/stack%3Aframework-django` on the api origin; authentication not required, approval not required)  
- Browse Deploy web app (`GET /v1/catalog/nodes/intent%3Adeploy-web-app` on the api origin; authentication not required, approval not required)

Actions describe possible next steps. They are typed data, not commands, and grant no permission. Public discovery never provisions anything; planning requires your own authenticated token and approval happens in your client.

## Identifiers and status

Recipe `page:blueprints:tutoring-centers:member-portal:django`. Revision r1.

release **published** support **verified** execution **blocked (schema_changed: live tool schema differs from the recorded binding)**