Course creators: event registration using Laravel · Ample Computer

Course creators: event registration using Laravel

An event registration blueprint for course creators built with Laravel on Ample. Domain schema:

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. Recordings and progress data are personal data; materials are authorized per course group. Technical basis verified on Laravel: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected).

What it runs on

You need

Exact tested configuration

Steps

  1. Model the course creators domain. Create the tables course_groups, memberships, sessions, materials, events. Cohorts as course groups lives in course_groups; keep the sensitive classes (learner progress and grades, recordings showing learners, payment status) out of this schema.

  2. Workflow step 1. Model sessions with capacity and registrations with status

  3. Workflow step 2. Register transactionally with a capacity check and an event per registration

  4. Workflow step 3. Reject stale concurrent updates

  5. Workflow step 4. Deploy and verify history and conflict handling

  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 --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/transactional-workflows) and your own acceptance checks for the course creators workflow.
   $ ample logs <deployment_id> --kind build

How it was checked

Evidence

  1. November 6, 2026 · canary run
    Laravel pattern fixture deployed on Ample (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); the transactional workflows checks passed: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). The blueprint's Course creators schema and workflow below build on that verified basis.

Tested examples

What it doesn’t cover