Professional training: member portal using Django · Ample Computer

Professional training: member portal using Django

A member portal blueprint for professional training built with Django on Ample. Domain schema:

Public information includes certification catalog, cohort dates, and trainer credentials. Exam results and certifications are personal records; only cohort logistics and 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).

What it runs on

You need

Exact tested configuration

install python3 -m pip install --target .ample/python -r requirements.txt
runtime python
sizes-1vcpu-1gb
start PYTHONPATH=.ample/python:${PYTHONPATH:-} python3 run.py
template python-3.12

Steps

  1. Model the professional training domain. Create the tables course_groups, memberships, sessions, materials, document_access. Certification cohorts live in course_groups; keep sensitive classes (exam results, employer billing, participant identity) 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 professional training 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; 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 Professional training schema and workflow below build on that verified basis.

Tested examples

What it doesn’t cover