# Membership associations: asset library using Next.js

An asset library blueprint for membership associations built with Next.js on Ample. Domain schema:  
- **course_groups** (chapter_or_program, start_at, end_at): chapters and programs as groups;  
- **memberships** (course_group_id, member_email, tier, role, renewed_at): members and roles;  
- **sessions** (course_group_id, starts_at, title, venue): meetings and events;  
- **materials** (course_group_id, title, object_key, visibility): member resources;  
- **uploads** (id, owner_reference, object_key, content_type, size, uploaded_at): validated uploads linked to their owner.  
Public information: about, chapters and benefits, public events, join information. Kept out of scope until handling is reviewed: member directory details, dues and payment records. Member directories are personal data; only public events and member-authorized resources 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

- [Computeverified](/content/discover/primitive/compute/index.html)  
  Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

- [Postgresverified](/content/discover/primitive/postgres/index.html)  
  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 storageverified](/content/discover/primitive/s3-compatible-object-storage/index.html)  
  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 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 membership associations data classes may be handled at all; this blueprint models public information only

## 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 membership associations domain.** Create the tables course_groups, memberships, sessions, materials, uploads. Chapters and programs as groups live in course_groups; keep the sensitive classes (member directory details, dues and payment 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.

```sh
   $ 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 membership associations workflow.

```sh
   $ 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 Membership associations schema and workflow below build on that verified basis.

## Tested examples

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

## What it doesn’t cover

- The technical basis (browser file uploads on Next.js) was verified with the pattern fixture; the membership associations schema and workflow are an original design for this blueprint, built on that basis.
- Member directories are personal data; only public events and member-authorized resources are modeled.
- Verified on the node-22 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.
