## Host admin dashboard with Laravel: tenant-scoped workspaces

### Summary
Deploy an admin dashboard built with Laravel on Ample using the multi-tenant relational data 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. Verified on Laravel: a tenant column on every row and query, with a cross-tenant read returning nothing (tenant_isolation=ok). Not separately tested: your tenant model, membership and per-tenant authorization; treat the admin dashboard-specific behavior as your application code.

### Representative Queries
- Host admin dashboard with Laravel: tenant-scoped workspaces
- Where can I host Admin dashboard built with Laravel?
- I need an explicit tenant model and application-enforced tenant isolation tests.

### Prerequisites
1. 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)
2. A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)
3. An Ample account token with servers:write, databases:read

### Workflow Steps
#### 1. Build and start
Run `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 multi-tenant relational data: a tenant column on every row and query, with a cross-tenant read returning nothing (tenant_isolation=ok). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.

#### 3. Deploy
Run `ample deploy . --name your_app_name --public` once and read the result (exit 0 live, 1 failed, 2 blocked). Re-running with no change is a no-op.

#### 4. Verify
Fetch the live URL and the pattern self-test route(s) (/p/multi-tenant-relational-data) from the example; then run your own checks. On failure read `ample logs --kind build` then `--kind runtime`.

### Examples
- **Laravel pattern fixture**: Multi-pattern Laravel app whose multi-tenant relational data module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
  - Source Reference: `tests/deploy-canaries/laravel-patterns`

### 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 admin dashboard itself (your tenant model, membership, and per-tenant authorization) 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.

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

### Evidence Summary
1. **Canary run**: Laravel pattern fixture deployed on Ample; checks passed for multi-tenant-relational-data and configuration-secrets. 
   - Observed At: 2026-09-20T20:36:21Z
   - Implementation Revision: `118ad1c6d7d23d4c2ce069254bab9ec9d37cd57b-dirty (CLI 118ad1c)`
   - Expires At: 2027-03-19T20:36:21Z

### Next Actions
1. **Browse the catalog index**: GET /v1/catalog 
2. **Search published recipes** by intent, stack, and constraints: POST /v1/catalog/search 
   - Body: {"limit":5,"query":"Host admin dashboard with Laravel: tenant-scoped workspaces"}
3. **Prepare a side-effect-free deployment plan**: POST /v1/catalog/plan 
   - Body: {"inputs":{},"projectId":"","recipeId":"page:recipes:admin-dashboard:laravel:tenant-workspaces","recipeRevision":"r1"}
4. **Read the existing agent authentication setup**: GET /mcp/setup
5. **Browse Admin dashboard**: GET /v1/catalog/nodes/workload%3Aadmin-dashboard
6. **Browse Laravel**: GET /v1/catalog/nodes/stack%3Aframework-laravel
7. **Browse Multi-tenant relational data**: GET /v1/catalog/nodes/pattern%3Amulti-tenant-relational-data
8. **Browse Deploy web app**: GET /v1/catalog/nodes/intent%3Adeploy-web-app