Photography studios: documentation site using Laravel · Ample Computer
Photography studios: documentation site using Laravel
A documentation site 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;
- state_transitions (record_type, from_state, to_state): the allowed state machine.
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 workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true).
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.CDNverified
A published bucket's objects are served from its public URL; set Cache-Control when uploading to control caching. App responses are served by the app.
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 and a published bucket for public assets (CDN_*) - A review of which photography studios data classes may be handled at all; this blueprint models public information only
Exact tested configuration
installcomposer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader
runtimephp
sizes-1vcpu-1gb
startfrankenphp php-server --listen :$PORT --root public
templatephp-8.5
Steps
- Model the photography studios domain. Create the tables listings, agencies, galleries, reports, state_transitions. 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.
- Workflow step 1. Model versioned documents with a state machine (draft, review, published) scoped to a product version
- Workflow step 2. Publish assets for released versions to the CDN bucket
- Workflow step 3. Serve only published versions publicly
- Workflow step 4. Deploy and verify the version list and a published page
- 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=... --env CDN_PUBLIC_URL=...
- Verify. Run the pattern self-test(s) from the example (/p/relational-records) and your own acceptance checks for the photography studios workflow.
$ ample logs <deployment_id> --kind build
How it was checked
✓app responds on its public URL· http get/ → “ample canary laravel patterns”
✓relational-records self-test from the example· http get/p/relational-records → “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 relational records checks passed: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). The blueprint's Photography studios schema and workflow below build on that verified basis.
Tested examples
- Laravel pattern fixture. Verified relational records basis for this blueprint.
What it doesn’t cover
- The technical basis (relational records on Laravel) was verified with the pattern fixture; the photography studios schema and workflow are an original design for this blueprint, built on that basis.
- 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.
- 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.