Membership associations: event registration using Laravel · Ample Computer

Membership associations: event registration using Laravel

An event registration blueprint for membership associations built with Laravel on Ample. Domain schema:
course_groups (chapter_or_program, start_at, end_at): chapters and programs as groups;
memberships (course_group_id, member_email, tier, role, renewed_at): members and roles;
sessions (course_group_id, starts_at, title, venue): meetings and events;
materials (course_group_id, title, object_key, visibility): member resources;
events (seq, record_type, record_id, kind, at): application-owned history written in the same transaction.
Public information: about, chapters and benefits, public events, join information.
Kept out of scope until handling is reviewed: member directory details, dues and payment records. Member directories are personal data; only public events and member-authorized resources are modeled.
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

installcomposer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader
runtimephp
sizes-1vcpu-1gb
startfrankenphp php-server --listen :$PORT --root public
templatephp-8.5

Steps

  1. Model the membership associations domain. Create the tables course_groups, memberships, sessions, materials, events. Chapters and programs as groups lives in course_groups; keep the sensitive classes (member directory details, dues and payment records) 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 membership associations workflow.
   $ ample logs <deployment_id> --kind build

How it was checked

✓ app responds on its public URL· http get/ → “ample canary laravel patterns”
✓ transactional-workflows self-test from the example· http get/p/transactional-workflows → “see the pattern fixture checks”

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 Membership associations schema and workflow below build on that verified basis.

Tested examples

What it doesn’t cover