page:blueprints:course creators:asset library:next js

Course creators: asset library using Next.js

Summary

A 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).

Representative Queries

Course creators: asset library using Next.js
Where can I host Course creators: Asset library built with Next.js?
I need a genuinely specialized asset library workflow covering course structure, member entitlements and downloadable materials.

Resource Requirements

primitive:compute
primitive:postgres
primitive:s3-compatible-object-storage

Infrastructure Requirements

Compute: Verified Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
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.
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 Next.js project (next build then next start -H 0.0.0.0 -p $PORT on the node-22 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 course creators data classes may be handled at all; this blueprint models public information only

Tested Configuration

Template: node-22
Runtime: node
Size: s-1vcpu-1gb
Install: npm install
Build: npm run build --if-present
Start: npm run start

Next Actions

Browse the catalog index: GET /v1/catalog
Search published recipes: POST /v1/catalog/search
Prepare a deployment plan: POST /v1/catalog/plan
Read existing authentication setup: GET /mcp/setup
Browse Course creators: GET /v1/catalog/nodes/industry%3Acourse-creators
Browse Asset library: GET /v1/catalog/nodes/workload%3Aasset-library
Browse Next.js: GET /v1/catalog/nodes/stack%3Aframework-next-js
Browse Deploy web app: GET /v1/catalog/nodes/intent%3Adeploy-web-app

Workflow Steps

Model the course creators domain: Create the tables course_groups, memberships, sessions, materials, uploads. Cohorts as course groups live in course_groups; keep sensitive classes out of this schema.
Workflow step 1: Model assets linked to their owning group or workspace
Workflow step 2: Validate uploads and store them in the private bucket; link each object to its row.
Workflow step 3: Authorize downloads by membership.
Workflow step 4: Deploy and verify rejection of disallowed files and a linked upload.
Deploy: Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
- Command: ample deploy . --name --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...
Verify: Run the pattern self-test(s) from the example and your own acceptance checks for the course creators workflow.
- Command: ample logs --kind build

Success Checks

App responds on its public URL: [GET /] expects "ample canary next js patterns"
Browser-file-uploads self-test from the example: [GET /p/browser-file-uploads] expects "see the pattern fixture checks"

Limitations

The technical basis was verified; the course creators schema and workflow are an original design and were not executed as a separate application.
No health, financial, privacy or other compliance claim is made. Recordings and progress data are personal data; materials are authorized per course group.
Public content and synthetic examples only until actual data-handling requirements have been reviewed.
Verified on the node-22 template at s-1vcpu-1gb; other sizes are unknown or unverified.
Only managed PostgreSQL 16 is verified; other limits are not verified.

Cost Estimate

Currency: USD
Monthly Amount: 10.0
Basis: Size prices from pricing.toml (loaded by the API)
Components:
- App server: s-1vcpu-1gb - $5.0
- Managed PostgreSQL database: s-1vcpu-1gb - $5.0
Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

Evidence Summary

Kind: canary_run
Summary: Next.js pattern fixture deployed on Ample (next build then next start). The browser file uploads checks passed. The blueprint's course creators schema and workflow build on that verified basis.