Course creators: member portal using Laravel

Summary

A member portal blueprint for course creators built with Laravel on Ample. Domain schema:

• course_groups (name, start_at, end_at, capacity): cohorts as course groups;
• memberships (course_group_id, member_email, role, joined_at): learner and instructor membership;
• sessions (course_group_id, starts_at, title, recording_object_key): session events and recordings;
• materials (course_group_id, title, object_key, visibility): teaching materials;
• document_access (document_id, principal_reference, role, granted_at): who may read which document.
  Public information: course catalog and syllabus, instructor profile, schedule. Kept out of scope until handling is reviewed: learner progress and grades, recordings showing learners, payment status.

Infrastructure requirements

• Compute: verified (Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.)
• Postgres: 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: verified (Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.)

Prerequisites

• A Laravel project (composer install --no-dev from composer.lock, then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 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 course creators data classes may be handled at all; this blueprint models public information only

Exact tested configuration

• template: php-8.5
• runtime: php
• size: s-1vcpu-1gb
• install: composer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader
• start: frankenphp php-server --listen :$PORT --root public

Steps

1. Model the course creators domain. Create the tables course_groups, memberships, sessions, materials, document_access.

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

   ample deploy . --name <app-name> --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...
   

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

   ample logs <deployment_id> --kind build
   

Tested examples

• Laravel pattern fixture (tests/deploy-canaries/laravel-patterns): Verified private document library basis for this blueprint.

Success checks

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

Limitations

• The technical basis (private document library on Laravel) was verified with the pattern fixture; the course creators 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. Recordings and progress data are personal data; materials are authorized per course group.
• Verified on the php-8.5 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.