Sports clubs: asset library using Next.js · Ample Computer

Sports clubs: asset library using Next.js

An asset library blueprint for sports clubs built with Next.js 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 Next.js: 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

You need

Exact tested configuration

build npm run build --if-present

install npm install

runtime node

sizes-1vcpu-1gb

start npm run start

template node-22

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=...
  1. 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 next js patterns”
✓ browser-file-uploads self-test from the example· http get/p/browser-file-uploads → “see the pattern fixture checks”

Evidence

  1. November 5, 2026 · canary run

Next.js pattern fixture deployed on Ample (next build then next start -H 0.0.0.0 -p $PORT on the node-22 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 build on that verified basis.

Tested examples

What it doesn’t cover