## Host community forum with Laravel: public profile assets

Deploy a community forum built with Laravel on Ample using the public image delivery 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: public objects in a published bucket served from the CDN URL, kept separate from private objects in an unpublished bucket that require authorization (private=ok only for the allowed role). Not separately tested: your image processing and profile-media rules; treat the community forum-specific behavior as your application code.

### Representative Queries
- Host community forum with Laravel: public profile assets
- Where can I host Community forum built with Laravel?
- I need separate public profile media from private data, with CDN cache rules.

### Resource Requirements
- primitive:compute
- primitive:postgres
- primitive:s3-compatible-object-storage
- primitive:cdn

### 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 image delivery: public objects in a published bucket served from the CDN URL, kept separate from private objects in an unpublished bucket that require authorization (private=ok only for the allowed role). 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.  
   `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, /p/private-document-library) from the example; then run your own checks. On failure read `ample logs --kind build` then `--kind runtime`.  
   `ample logs --kind build`

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

### 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 community forum itself (your image processing and profile-media rules) is application code and was not separately tested; the pattern checks are what was verified.

### Cost Estimate
- Currency: USD
- Monthly Amount: 10.0
- Components:
  - app server (size: s-1vcpu-1gb): $5.0
  - managed PostgreSQL database (size: s-1vcpu-1gb): $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; checks passed for public-media-library, private-document-library and configuration-secrets.
  - Observed At: 2026-09-20T20:36:21Z

### Next Actions
- **Browse the catalog index** (GET /v1/catalog)
- **Search published recipes by intent, stack and constraints** (POST /v1/catalog/search)