## The short version An asset library blueprint for photography studios built with Laravel on Ample. Domain schema: listings (reference, session_type, price_from, publishing_status, agency_id): session packages with publishing status; agencies (name, location, studio_count): studios or locations; galleries (listing_id, object_key, cdn_key, consent_reference): published portfolio media; reports (agency_id, period, object_key, generated_at): studio booking reports; uploads (id, owner_reference, object_key, content_type, size, uploaded_at): validated uploads linked to their owner. Public information: session packages and pricing from, consented portfolio galleries, studio locations. Kept out of scope until handling is reviewed: client galleries before release, minors in photographs, payment details. Client galleries are private until released with consent; only consented portfolio media is public. 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 needs - [Compute](/content/discover/primitive/compute/index.html): verified (Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.) - [Postgres](/content/discover/primitive/postgres/index.html): verified (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](/content/discover/primitive/s3-compatible-object-storage/index.html): verified (Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.) ## Before you start - 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 create` passed as encrypted S3_* environment variables - A review of which photography studios data classes may be handled at all; this blueprint models public information only ## How to do it 1. 1 ### Model the photography studios domain Create the tables listings, agencies, galleries, reports, uploads. Session packages with publishing status lives in listings; keep the sensitive classes (client galleries before release, minors in photographs, payment details) out of this schema. 2. 2 ### Workflow step 1 Model assets linked to their owning group or workspace 3. 3 ### Workflow step 2 Validate uploads and store them in the private bucket; link each object to its row 4. 4 ### Workflow step 3 Authorize downloads by membership 5. 5 ### Workflow step 4 Deploy and verify rejection of disallowed files and a linked upload 6. 6 ### Deploy Run the synchronous deploy once and read the result. Re-running with no change is a no-op. ``` ample deploy . --name --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=... ``` 7. 7 ### Verify Run the pattern self-test(s) from the example (/p/browser-file-uploads) and your own acceptance checks for the photography studios workflow. ``` ample logs --kind build ``` ## Tested examples - **Laravel pattern fixture** (`tests/deploy-canaries/laravel-patterns`): Verified browser file uploads basis for this blueprint. ## How to know it worked - app responds on its public URL (`/` on the live URL, expect ample canary laravel patterns) - browser-file-uploads self-test from the example (`/p/browser-file-uploads` on the live URL, expect see the pattern fixture checks) ## Cost estimate Estimated 10.00 USD per month (size prices from pricing.toml at build revision ca0b484a7a9957c573a88d3a32dc603c3c10135a). - app server x1 `s-1vcpu-1gb`: 5.00 USD - managed PostgreSQL database x1 `s-1vcpu-1gb`: 5.00 USD Upper-bound monthly price of the tested sizes. Buckets are allocation-priced per quota and not included. ## Verification evidence - canary_run on 2026-09-20T20:36:21Z at revision `118ad1c6d7d23d4c2ce069254bab9ec9d37cd57b (CLI 118ad1c)`: 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 Photography studios schema and workflow below build on that verified basis and were not separately executed. (expires 2027-03-19T20:36:21Z) ## Execution binding MCP tool `ample_deploy` (registry `mcp:ample_deploy`), schema hash `876465fce906da0c` observed 2026-09-22T00:31:22.774679+00:00 at revision `e6446ceea69b`. Binding state at export: schema_changed. Required scopes: servers:write, databases:read, buckets:read. ## Typed next actions - Browse the catalog index (`GET /v1/catalog` on the api origin; authentication not required, approval not required) - Search published recipes by intent, stack and constraints (`POST /v1/catalog/search` on the api origin; authentication not required, approval not required) - Prepare a side-effect-free deployment plan for an authorized project (`POST /v1/catalog/plan` on the api origin; authentication required, approval not required) - Read the existing agent authentication setup (`GET /mcp/setup` on the api origin; authentication not required, approval not required) - Browse Photography studios (`GET /v1/catalog/nodes/industry%3Aphotography-studios` on the api origin; authentication not required, approval not required) - Browse Asset library (`GET /v1/catalog/nodes/workload%3Aasset-library` on the api origin; authentication not required, approval not required) - Browse Laravel (`GET /v1/catalog/nodes/stack%3Aframework-laravel` on the api origin; authentication not required, approval not required) - Browse Deploy web app (`GET /v1/catalog/nodes/intent%3Adeploy-web-app` on the api origin; authentication not required, approval not required) Actions describe possible next steps. They are typed data, not commands, and grant no permission. Public discovery never provisions anything; planning requires your own authenticated token and approval happens in your client.