# Photography studios: client portal using Laravel

## Summary
A client portal 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;  
- **Document Access** (document_id, principal_reference, role, granted_at): who may read which document.

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: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok).

## Representative Queries
- Photography studios: client portal using Laravel
- Where can I host Photography studios: Client portal built with Laravel?
- I need a genuinely specialized client portal workflow covering client galleries, usage permissions and original/derivative assets.

## Resource Requirements
- **Primitive Compute**  
- **Primitive PostgreSQL**  
- **Primitive S3-Compatible Object Storage**

## Infrastructure Requirements
- **Compute**:  
  Summary: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.  
- **Postgres**:  
  Summary: 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**:  
  Summary: 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, document_access. 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 client entities and engagement periods; every document belongs to one engagement.  
3. **Workflow step 2**  
Authorize by client entity and role before any storage access (401 without identity, 403 for the wrong client).  
4. **Workflow step 3**  
Store documents in the private bucket and stream them through the app.  
5. **Workflow step 4**  
Deploy and verify the negative authorization tests and an authorized download.  
6. **Deploy**  
Run the synchronous deploy once and read the result. Re-running with no change is a no-op.  
7. **Verify**  
Run the pattern self-test(s) from the example (/p/private-document-library) and your own acceptance checks for the photography studios workflow.

## Examples
- **Laravel pattern fixture**: Verified private document library basis for this blueprint.

## Success Checks
- **HTTP Get**: app responds on its public URL 
- **HTTP Get**: private-document-library self-test from the example

## Limitations
- The technical basis (private document library 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.
- No health, financial, privacy or other compliance claim is made. 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.
- Managed PostgreSQL 16 only; extensions, connection limits, and backup or restore procedures are not verified.
- PutObject and GetObject with path-style addressing are verified; other S3 operations and CDN cache rules are not.

## Cost Estimate
- **Currency**: USD  
- **Monthly Amount**: 10.0  
- **Basis**: size prices from pricing.toml

## Evidence Summary
- **Kind**: canary_run  
- **Summary**: Laravel pattern fixture deployed on Ample; the private document library checks passed.

## Next Actions
- **Browse the catalog index**  
- **Search published recipes by intent, stack and constraints**  
- **Prepare a side-effect-free deployment plan for an authorized project**  
- **Read the existing agent authentication setup**  
- **Browse Photography studios**  
- **Browse Client portal**  
- **Browse Laravel**  
- **Browse Deploy web app**