Photography studios: asset library using Laravel

Summary

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

Representative Queries

• Photography studios: asset library using Laravel
• Where can I host Photography studios: Asset library built with Laravel?
• I need a genuinely specialized asset library workflow covering client galleries, usage permissions and original/derivative assets.

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.

Workflow Steps

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. 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 photography studios workflow.
   • Command: ample logs --kind build

Limitations

• The technical basis (browser file uploads on Laravel) was verified with the pattern fixture; the photography studios schema and workflow are an original design for this blueprint and were not executed as a separate application.
• Client galleries are private until released with consent; only consented portfolio media is public.
• Verified on the php-8.5 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Components:
  • App server: s-1vcpu-1gb - $5.00
  • Managed PostgreSQL database: s-1vcpu-1gb - $5.00

Evidence Summary

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

Next Actions

• Browse the catalog index: [GET] /v1/catalog
• Search published recipes by intent, stack and constraints: [POST] /v1/catalog/search
• Prepare a side-effect-free deployment plan for an authorized project: [POST] /v1/catalog/plan
• Read the existing agent authentication setup: [GET] /mcp/setup
• Browse Photography studios: [GET] /v1/catalog/nodes/industry%3Aphotography-studios
• Browse Asset library: [GET] /v1/catalog/nodes/workload%3Aasset-library
• Browse Laravel: [GET] /v1/catalog/nodes/stack%3Aframework-laravel
• Browse Deploy web app: [GET] /v1/catalog/nodes/intent%3Adeploy-web-app