page:blueprints:course creators:event registration:laravel

Course creators: event registration using Laravel

Summary

A event registration 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;
• events (seq, record_type, record_id, kind, at): application-owned history written in the same transaction.

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.

Resource Requirements

• primitive:compute
• primitive:postgres
• primitive:s3-compatible-object-storage

Infrastructure Requirements

1. Compute: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
2. Postgres: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
3. S3-compatible object storage: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

Framework and Workload

• Framework: Laravel
• Workload: Event registration
• Industry: Course creators

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

Workflow Steps

1. Model the course creators domain: Create the tables course_groups, memberships, sessions, materials, events. Cohorts as course groups live in course_groups; keep the sensitive classes 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.
   • Command: ample deploy . --name --public --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/transactional-workflows) and your own acceptance checks for the course creators workflow.
   • Command: ample logs --kind build

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

Success Checks

1. App responds on its public URL: Expect Response from ample canary laravel patterns.
2. Transactional-workflows self-test from the example: Expect to see the pattern fixture checks.

Limitations

• Public content and synthetic examples only until actual data-handling requirements have been reviewed.
• The technical basis (transactional workflows 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.

Examples

• Title: Laravel pattern fixture
  • Description: Verified transactional workflows basis for this blueprint.
  • Source Ref: tests/deploy-canaries/laravel-patterns