Course creators: asset library using Laravel · Ample Computer

Course creators: asset library using Laravel

An asset library blueprint for course creators built with Laravel on Ample. Domain schema:

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

You need

Exact tested configuration

install

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 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 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 Course creators schema and workflow below build on that verified basis.

Tested examples

What it doesn’t cover