Course creators: asset library using Next.js · Ample Computer

Course creators: asset library using Next.js

An asset library blueprint for course creators built with Next.js on Ample. Domain schema:
course_groups (name, start_at, end_at, capacity): cohorts as course groups;
memberships (course_group_id, member_email, role, joined_at): learner and instructor membership;
sessions (course_group_id, starts_at, title, recording_object_key): session events and recordings;
materials (course_group_id, title, object_key, visibility): teaching materials;
uploads (id, owner_reference, object_key, content_type, size, uploaded_at): validated uploads linked to their owner.
Public information: course catalog and syllabus, instructor profile, schedule. Kept out of scope until handling is reviewed: learner progress and grades, recordings showing learners, payment status.
Recordings and progress data are personal data; materials are authorized per course group.
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 course creators domain. Create the tables course_groups, memberships, sessions, materials, uploads. Cohorts as course groups lives in course_groups; keep the sensitive classes (learner progress and grades, recordings showing learners, payment status) 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 course creators 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 Course creators schema and workflow below build on that verified basis.

Tested examples

What it doesn’t cover