# Host public directory with Laravel: Postgres-backed content

Deploy a public directory 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 public directory-specific behavior as your application code.

## Representative Queries
- Host public directory with Laravel: Postgres-backed content
- Where can I host Public directory 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

1. **Compute**  
   Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.

2. **Postgres**  
   Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

3. **CDN**  
   The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.

## Framework
Laravel

## Workload
Public directory

## Execution Status
Ready

## 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
- An Ample account token with servers:write, databases:read, buckets:read

## Tested Configuration
- **Template:** php-8.5  
- **Runtime:** php  
- **Size:** s-1vcpu-1gb  
- **Install:** composer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader  
- **Start:** 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 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.  
   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/relational-records) 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

- **Relational-records self-test**  
  Kind: http_get  
  Path: /p/relational-records  
  Expect: 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 public directory itself (your record schema, states and access rules) is application code and was not separately tested; the pattern checks are what was verified.

## Cost Estimate
- **Currency:** USD  
- **Monthly Amount:** 10.0  
- **Basis:** size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty

### Components
- **App server**  
  Size: s-1vcpu-1gb  
  Quantity: 1.0  
  Monthly Amount: 5.0

- **Managed PostgreSQL database**  
  Size: 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.

## Evidence Summary
- **Kind:** canary_run  
  **Summary:** 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); checks passed for relational-records and configuration-secrets. Pattern proof: 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).
  **Observed At:** 2026-09-20T20:36:21Z

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