## Host campaign site with Laravel: Postgres-backed content

Deploy a campaign site built with Laravel on Ample using the relational records 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, and a published bucket serves public assets from the CDN host. 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). Not separately tested: your record schema, states and access rules; treat the campaign site-specific behavior as your application code.

### Representative Queries  
- Host campaign site with Laravel: Postgres-backed content  
- Where can I host Campaign site built with Laravel?  
- I need a content schema, publishing workflow and cache behavior after content updates.

### Resource Requirements  
- primitive:compute  
- primitive:postgres  
- primitive:cdn

### 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.
  
- **CDN**  
  Summary: The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.

### Execution Status  
- **Framework:** Laravel  
- **Workload:** Campaign site  
- **Release Status:** published  
- **Support Status:** verified  
- **Execution Status:** ready

### Prerequisites  
1. A Laravel project that builds and starts with 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)  
2. A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)  
3. A bucket from `ample bucket create` with its credentials passed as encrypted S3_* environment variables  
4. 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 relational records: 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). 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.  
5. **Verify**  
   - Fetch the live URL and the pattern self-test route(s) (/p/relational-records) from the example; then run your own checks. On failure read `ample logs  --kind build` then `--kind runtime`.

### Success Checks  
1. **App responds on its public URL**  
   - Expected: `ample canary laravel patterns`  
2. **Relational-records self-test**  
   - Expected: `records=ok transitions=true isolation=true`

### 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 campaign site itself (your record schema, states and access rules) 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.

### Cost Estimate  
- **Total:** 10.0 USD/month  
- **Components:**  
  - app server: s-1vcpu-1gb, quantity: 1.0, monthly amount: 5.0  
  - managed PostgreSQL database: s-1vcpu-1gb, quantity: 1.0, monthly amount: 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.

### 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 Campaign site  
- Browse Laravel  
- Browse Relational records  
- Browse Deploy web app

### Evidence Summary  
1. **Kind:** canary_run  
   - Summary: Laravel pattern fixture deployed on Ample; checks passed for relational-records and configuration-secrets.  
   - Observed At: 2026-09-20T20:36:21Z  
   - Expires At: 2027-03-19T20:36:21Z  
2. **Kind:** canary_run  
   - Summary: Same Laravel app deployed with a --release-command migration; the marker it created was readable after activation.  
   - Observed At: 2026-09-20T20:36:21Z  
   - Expires At: 2027-03-19T20:36:21Z

### Last Verified At  
- 2026-09-20T20:36:21Z
