# Sports clubs: asset library using Laravel

An 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, 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).

## What it runs on

- **Compute**  
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

- **Postgres**  
Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

- **S3-compatible object storage**  
Buckets speak the S3 API with SigV4 credentials Ample Computer issues; `ample bucket upload-url` returns a presigned upload URL. PutObject and GetObject are checked by canary.

## You need

- 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

## Exact tested configuration

- `composer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader`  
- Runtime: php  
- Sizes: 1vcpu-1gb  
- Start: `frankenphp php-server --listen :$PORT --root public`  
- Template: php-8.5

## 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.

```
   $ 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=...
   ```

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.

```
   $ ample logs <deployment_id> --kind build
   ```

## How it was checked

- ✓ app responds on its public URL · http get/ → “ample canary laravel patterns”  
- ✓ browser-file-uploads self-test from the example · http get/p/browser-file-uploads → “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 browser file uploads checks passed: 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). The blueprint's Sports clubs schema and workflow below build on that verified basis.

## Tested examples

- **Laravel pattern fixture.** Verified browser file uploads basis for this blueprint.

## What it doesn’t cover

- 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, built on that basis.
- Medical and safeguarding records are sensitive; only schedules and coaching materials are modeled.
- Verified on the php-8.5 template at s-1vcpu-1gb.
- Managed PostgreSQL 16 with pgvector.
- Buckets speak the standard S3 API (PutObject and GetObject with path-style addressing are checked by the fixture); `ample bucket upload-url` returns presigned upload URLs.
