Nonprofits: asset library using Laravel · Ample Computer
Nonprofits: asset library using Laravel
An asset library blueprint for nonprofits built with Laravel 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. Beneficiary and donor data are sensitive; donations are handled by your payment provider. 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
Computeverified
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.Postgresverified
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
Buckets speak the S3 API with SigV4 credentials Ample Computer issues;ample bucket upload-urlreturns a presigned upload URL. PutObject and GetObject are checked by canary.
You need
- A Laravel project (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)
- A PostgreSQL driver reading DATABASE_URL (auto-provisioned when omitted)
- Bucket credentials from
ample bucket createpassed as encrypted S3_* environment variables - A review of which nonprofits data classes may be handled at all; this blueprint models public information only
Exact tested configuration
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
- Model the nonprofits domain. Create the tables course_groups, memberships, sessions, materials, uploads. Programs and cohorts lives in course_groups; keep the sensitive classes (beneficiary identity and case notes, donor records) 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.
$ 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=...
- Verify. Run the pattern self-test(s) from the example (/p/browser-file-uploads) and your own acceptance checks for the nonprofits 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
- 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 Nonprofits schema and workflow below build on that verified basis.
Tested examples
- Laravel pattern fixture. Verified browser file uploads basis for this blueprint.
What it doesn’t cover
- The technical basis (browser file uploads on Laravel) was verified with the pattern fixture; the nonprofits schema and workflow are an original design for this blueprint, built on that basis.
- Beneficiary and donor data are sensitive; donations are handled by your payment provider.
- Verified on the php-8.5 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-urlreturns presigned upload URLs.