# Host product catalog with Laravel: public product media

Deploy a product catalog built with Laravel on Ample using the public media library pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, a managed PostgreSQL 16 database is auto-provisioned and injected as DATABASE_URL, a private S3-compatible bucket holds objects with credentials delivered as encrypted environment variables, and a published bucket serves public assets from the CDN host. Verified on Laravel: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly. Not separately tested: your media processing, object layout and cache policy; treat the product catalog-specific behavior as your application code.

## Representative Queries
- Host product catalog with Laravel: public product media
- Where can I host Product catalog built with Laravel?
- I need product-to-object mappings and a tested public media delivery path.

## Prerequisites
- A Laravel project that builds and starts with the documented commands (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 at runtime (auto-provisioned when omitted, or supplied with --env)
- A bucket from `ample bucket create` with its credentials passed as encrypted S3_* environment variables and a second, published bucket for public assets (CDN_*)
- An Ample account token with servers:write, databases:read, buckets:read

## Workflow Steps
1. **Build and start**  
   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 server must bind 0.0.0.0 on PORT.

2. **Implement the pattern on PostgreSQL**  
   The fixture's module implements public media library: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly. Copy the approach into your schema; keep migrations idempotent and run them with --release-command.

3. **Wire object storage**  
   Create the bucket(s), then pass endpoint, region, bucket and keys as --env values. Use path-style addressing. Keep private data in an unpublished bucket. Publish only the bucket that serves public assets and reference its CDN URL.

4. **Deploy**  
   Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 blocked). 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=... --env CDN_PUBLIC_URL=...

5. **Verify**  
   Fetch the live URL and the pattern self-test route(s) (/p/public-media-library) from the example; then run your own checks. On failure read `ample logs  --kind build` then `--kind runtime`.  
   Command: ample logs  --kind build

## Examples
- **Laravel pattern fixture**  
   Multi-pattern Laravel app whose public media library module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

## Success Checks
- **App responds on its public URL**  
   Kind: http_get  
   Path: /  
   Expect: ample canary laravel patterns

- **Public-media-library self-test**  
   Kind: http_get  
   Path: /p/public-media-library  
   Expect: a CDN URL whose content is served publicly.

## Limitations
- Verified on the php-8.5 template at s-1vcpu-1gb with the example fixture; other sizes, templates and Laravel major versions are not verified.
- The product catalog itself (your media processing, object layout and cache policy) is application code and was not separately tested; the pattern checks are what was verified.
- Region, compliance attestations and request-duration limits are unknown and not claimed.
- Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.
- PutObject and GetObject with path-style addressing are verified; multipart upload, listing, presigned URLs and lifecycle rules are not.
- The CDN serves published-bucket objects only; cache rules, purge and TTL control are not verified (the fixture sets Cache-Control on upload and versions keys).

## Cost Estimate
- **Monthly Amount**: 10.0 **Currency**: USD  
  Basis: size prices from pricing.toml at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty  
  Components:
  - App server - size: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 5.0
  - Managed PostgreSQL database - size: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 5.0
  Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

## Evidence Summary
- **Canary Run**: Laravel pattern fixture deployed on Ample  
   Summary: checks passed for public-media-library and configuration-secrets. Pattern proof: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly.  
   Observed At: 2026-09-20T20:36:21Z  
   Implementation Revision: 118ad1c6d7d23d4c2ce069254bab9ec9d37cd57b-dirty (CLI 118ad1c)  
   Expires At: 2027-03-19T20:36:21Z

- **Canary Run**: The same Laravel app deployed with a --release-command migration; the marker it created was readable after activation.  
   Observed At: 2026-09-20T20:36:21Z  
   Implementation Revision: 118ad1c6d7d23d4c2ce069254bab9ec9d37cd57b-dirty (CLI 118ad1c)  
   Expires At: 2027-03-19T20:36:21Z

## Next Actions
- **Browse the catalog index**  
  Action ID: browse-catalog  
  Method: GET  
  Relative Path: /v1/catalog

- **Search published recipes by intent, stack and constraints**  
  Action ID: search-recipes  
  Method: POST  
  Relative Path: /v1/catalog/search  
  Parameters: {"body":{"limit":5,"query":"Host product catalog with Laravel: public product media"}}

- **Prepare a side-effect-free deployment plan for an authorized project**  
  Action ID: plan:page:recipes:product-catalog:laravel:product-media  
  Method: POST  
  Relative Path: /v1/catalog/plan  
  Parameters: {"body":{"inputs":{},"projectId":"","recipeId":"page:recipes:product-catalog:laravel:product-media","recipeRevision":"r1"}}

- **Read the existing agent authentication setup**  
  Action ID: auth-setup  
  Method: GET  
  Relative Path: /mcp/setup

- **Browse Product catalog**  
  Action ID: browse:workload:product-catalog  
  Method: GET  
  Relative Path: /v1/catalog/nodes/workload%3Aproduct-catalog

- **Browse Laravel**  
  Action ID: browse:stack:framework-laravel  
  Method: GET  
  Relative Path: /v1/catalog/nodes/stack%3Aframework-laravel

- **Browse Public media library**  
  Action ID: browse:pattern:public-media-library  
  Method: GET  
  Relative Path: /v1/catalog/nodes/pattern%3Apublic-media-library

- **Browse Deploy web app**  
  Action ID: browse:intent:deploy-web-app  
  Method: GET  
  Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app