page:blueprints:membership associations:event registration:laravel

Membership associations: event registration using Laravel

Summary

A event registration blueprint for membership associations built with Laravel on Ample. Domain schema:

Representative Queries

Resource Requirements

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.

Prerequisites

Workflow 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.
    • 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 membership associations workflow.
    • Command: ample logs --kind build

Limitations

Cost Estimate

Success Checks

  1. App responds on its public URL
    • Kind: http_get
    • Path: /
    • Expect: ample canary laravel patterns
  2. Transactional workflows self-test from the example
    • Kind: http_get
    • Path: /p/transactional-workflows
    • Expect: see the pattern fixture checks

Evidence Summary

Formats