Tutoring centers: member portal using Laravel

Summary

A member portal blueprint for tutoring centers built with Laravel on Ample. Domain schema:

• course_groups (subject, level, start_at, end_at, capacity): tutoring groups;
• memberships (course_group_id, student_reference, guardian_reference, role): students, guardians and tutors;
• sessions (course_group_id, starts_at, tutor, attendance_count): session events;
• materials (course_group_id, title, object_key, visibility): worksheets and answer keys;
• document_access (document_id, principal_reference, role, granted_at): who may read which document.

Public information: subjects and levels, schedule and locations, tutor qualifications. Kept out of scope until handling is reviewed: minor students and guardian identity, progress reports. Data about minors is sensitive; only group schedules and materials are modeled here.

Technical basis verified on Laravel: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok).

Representative Queries

1. Tutoring centers: member portal using Laravel
2. Where can I host Tutoring centers: Member portal built with Laravel?
3. I need a genuinely specialized member portal workflow covering course-group membership, session events and teaching materials.

Resource Requirements

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

Infrastructure Requirements

1. Compute
   • Summary: 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
   • Summary: 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
   • Summary: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

Workflow Steps

1. Model the tutoring centers domain
   • Create the tables course_groups, memberships, sessions, materials, document_access. Tutoring groups lives in course_groups; keep the sensitive classes (minor students and guardian identity, progress reports) out of this schema.
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
6. Deploy
   • 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
   • Command: ample logs --kind build

Examples

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

Success Checks

1. App responds on its public URL. Expect: ample canary laravel patterns.
2. Private-document-library self-test from the example. Expect: see the pattern fixture checks.

Limitations

• The technical basis (private document library on Laravel) was verified with the pattern fixture; the tutoring centers 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. Data about minors is sensitive; only group schedules and materials are modeled here.
• Public content and synthetic examples only until actual data-handling requirements have been reviewed.
• 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.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Authoritative: true
• Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
• Components:
  1. App server: size s-1vcpu-1gb, quantity 1.0, monthly amount 5.0
  2. Managed PostgreSQL database: size s-1vcpu-1gb, quantity 1.0, monthly amount 5.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.

Evidence Summary

• Kind: canary_run
  • Summary: 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 private document library checks passed: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok). The blueprint's Tutoring centers schema and workflow below build on that verified basis and were not separately executed.
  • Observed At: 2026-09-20T20:36:21Z
  • Implementation Revision: 118ad1c6d7d23d4c2ce069254bab9ec9d37cd57b-dirty (CLI 118ad1c)
  • Expires At: 2027-03-19T20:36:21Z
  • Scope: checks=[/p/private-document-library], pattern=pattern:private-document-library, template=php-8.5

Last Verified At

2026-09-20T20:36:21Z

Unknowns

• Region availability is unknown until a verified region fact is recorded.
• Compliance attestations are unknown; none are claimed.

Formats

• HTML: View as HTML
• Markdown: View as Markdown
• JSON: View as JSON

Next Actions

1. Browse the catalog index - [GET /v1/catalog]
2. Search published recipes by intent, stack and constraints - [POST /v1/catalog/search]
3. Prepare a side-effect-free deployment plan for an authorized project - [POST /v1/catalog/plan]
4. Read the existing agent authentication setup - [GET /mcp/setup]
5. Browse Tutoring centers - [GET /v1/catalog/nodes/industry%3Atutoring-centers]
6. Browse Member portal - [GET /v1/catalog/nodes/workload%3Amember-portal]
7. Browse Laravel - [GET /v1/catalog/nodes/stack%3Aframework-laravel]
8. Browse Deploy web app - [GET /v1/catalog/nodes/intent%3Adeploy-web-app]