## Host documentation site with Laravel: object-stored public media

### Summary
Deploy a documentation site 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 documentation site-specific behavior as your application code.

### Representative Queries
- Host documentation site with Laravel: object-stored public media
- Where can I host Documentation site built with Laravel?
- I need an object layout, public asset URL policy and CDN delivery configuration.

### 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

### Tested Configuration
- **Template:** php-8.5
- **Runtime:** php
- **Size:** s-1vcpu-1gb
- **Install Command:** composer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader
- **Start Command:** frankenphp php-server --listen :$PORT --root public

### 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

### 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 documentation site 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.

### Cost Estimate
- **Currency:** USD
- **Monthly Amount:** 10.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:**  
  Summary: Laravel pattern fixture deployed on Ample...  
  Observed At: 2026-09-20T20:36:21Z

### Next Actions
- **Browse the catalog index**  
  - Operation ID: catalog_index
  - Method: GET
  - Relative Path: /v1/catalog  
- **Search published recipes by intent, stack and constraints**  
  - Operation ID: search_recipes  
  - Method: POST
  - Relative Path: /v1/catalog/search  
- **Prepare a side-effect-free deployment plan for an authorized project**  
  - Operation ID: plan_deployment  
  - Method: POST
  - Relative Path: /v1/catalog/plan