# Sports clubs: asset library using Laravel

## Summary
A asset library blueprint for sports clubs built with Laravel on Ample. Domain schema:
- **course_groups** (team_or_class, season, age_group): teams and classes;
- **memberships** (course_group_id, member_reference, guardian_reference, role): players, guardians and coaches;
- **sessions** (course_group_id, starts_at, venue, type): training and fixtures;
- **materials** (course_group_id, title, object_key, visibility): schedules and coaching resources;
- **uploads** (id, owner_reference, object_key, content_type, size, uploaded_at): validated uploads linked to their owner.

Public information: teams, seasons and fixtures, venues, membership fees. Kept out of scope until handling is reviewed: minor members and medical notes, safeguarding records. Medical and safeguarding records are sensitive; only schedules and coaching materials are modeled.

Technical basis verified on Laravel: content-type and size validation that rejects disallowed files, an object written to a private bucket and a row linking the record to the object key (reject=ok upload=ok linked=ok).

## Representative Queries
- Sports clubs: asset library using Laravel
- Where can I host Sports clubs: Asset library built with Laravel?
- I need a genuinely specialized asset library workflow covering team membership, event participation and club media.

## Resource Requirements
- **Compute**
- **Postgres**
- **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.

## 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 sports clubs data classes may be handled at all; this blueprint models public information only.

## Workflow Steps
1. Model the sports clubs domain: Create the tables course_groups, memberships, sessions, materials, uploads. Teams and classes live in course_groups; keep the sensitive classes (minor members and medical notes, safeguarding records) out of this schema.
2. **Workflow step 1**: Model assets linked to their owning group or workspace.
3. **Workflow step 2**: Validate uploads and store them in the private bucket; link each object to its row.
4. **Workflow step 3**: Authorize downloads by membership.
5. **Workflow step 4**: Deploy and verify rejection of disallowed files and a linked upload.
6. **Deploy**: Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
7. **Verify**: Run the pattern self-test(s) from the example (/p/browser-file-uploads) and your own acceptance checks for the sports clubs workflow.

## Examples
- **Laravel pattern fixture**: Verified browser file uploads basis for this blueprint. (sourceRef: tests/deploy-canaries/laravel-patterns)

## Success Checks
1. App responds on its public URL.
2. Browser-file-uploads self-test from the example.

## Limitations
- The technical basis (browser file uploads on Laravel) was verified with the pattern fixture; the sports clubs 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. Medical and safeguarding records are sensitive; only schedules and coaching materials are modeled.

## Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Components**: 
   - app server: size s-1vcpu-1gb, quantity 1.0, monthlyAmount 5.0
   - managed PostgreSQL database: size s-1vcpu-1gb, quantity 1.0, monthlyAmount 5.0
- **Note**: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

## Evidence Summary
- **Observation**: Laravel pattern fixture deployed on Ample. The browser file uploads checks passed: content-type and size validation that rejects disallowed files.

## Next Actions
1. Browse the catalog index
2. Search published recipes by intent, stack and constraints
3. Prepare a side-effect-free deployment plan for an authorized project.
