page:blueprints:nonprofits:asset library:next js

Nonprofits: asset library using Next.js

Summary

A asset library blueprint for nonprofits built with Next.js on Ample. Domain schema:

• course_groups (program, cohort, start_at, end_at): programs and cohorts;
• memberships (course_group_id, participant_reference, role): participants, volunteers and staff;
• sessions (course_group_id, starts_at, title, location): program sessions and events;
• materials (course_group_id, title, object_key, visibility): program materials;
• uploads (id, owner_reference, object_key, content_type, size, uploaded_at): validated uploads linked to their owner.
  Public information: mission and programs, events, donation entry point. Kept out of scope until handling is reviewed: beneficiary identity and case notes, donor records.

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

• Nonprofits: asset library using Next.js
• Where can I host Nonprofits: Asset library built with Next.js?
• I need a genuinely specialized asset library workflow covering program participation, volunteer events and program resources.

Resource Requirements

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

Infrastructure Requirements

• Compute: 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

1. A Next.js project (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template)
2. A PostgreSQL driver reading DATABASE_URL (auto-provisioned when omitted)
3. Bucket credentials from ample bucket create passed as encrypted S3_* environment variables
4. A review of which nonprofits data classes may be handled at all; this blueprint models public information only

Workflow Steps

1. Model the nonprofits domain: Create the tables course_groups, memberships, sessions, materials, uploads.
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. Command: ample deploy . --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 nonprofits workflow.
   Command: ample logs --kind build

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Authoritative: true
• Basis: size prices from pricing.toml (loaded by the API...)
• Components:
  • app server: size s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 5.0
  • managed PostgreSQL database: size s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 5.0
• Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

Examples

• Next.js pattern fixture: Verified browser file uploads basis for this blueprint. Source Ref: tests/deploy-canaries/next-js-patterns

Limitations

• The technical basis (browser file uploads on Next.js) was verified with the pattern fixture; the nonprofits schema and workflow are an original design for this blueprint and were not executed as a separate application.
• No health, financial, privacy or other compliance claim is made.
• Verified on the node-22 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.

Next Actions

1. Browse the catalog index
2. Search published recipes by intent, stack and constraints
3. Prepare a side-effect-free deployment plan for an authorized project
4. Read the existing agent authentication setup
5. Browse Nonprofits
6. Browse Asset library
7. Browse Next.js
8. Browse Deploy web app