### Host admin dashboard with Laravel: application activity history

Deploy an admin dashboard built with Laravel on Ample using the transactional workflows 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: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). Not separately tested: your domain records, validation rules and concurrency policy; treat the admin dashboard-specific behavior as your application code.

#### Representative Queries
- Host admin dashboard with Laravel: application activity history
- Where can I host Admin dashboard built with Laravel?
- I need an application-owned event schema and tested history queries; not native platform audit logs.

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

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

#### 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)
- An Ample account token with servers:write, databases: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 transactional workflows: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.

3. **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`

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

### Success Checks
- App responds on its public URL; expect **ample canary laravel patterns** at path **/**
- Transactional-workflows self-test; expect **tx=ok history=2 conflict=rejected** at path **/p/transactional-workflows**

### 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 domain records, validation rules, and concurrency policy) 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 (s-1vcpu-1gb): **5.0**
  - Managed PostgreSQL database (s-1vcpu-1gb): **5.0**
- Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

### Next Actions
- [Browse the catalog index](/v1/catalog)
- [Search published recipes by intent, stack and constraints](/v1/catalog/search)
- [Prepare a side-effect-free deployment plan for an authorized project](/v1/catalog/plan)
- [Read the existing agent authentication setup](/mcp/setup)
- [Browse Admin dashboard](/v1/catalog/nodes/workload%3Aadmin-dashboard)
- [Browse Laravel](/v1/catalog/nodes/stack%3Aframework-laravel)
- [Browse Transactional workflows](/v1/catalog/nodes/pattern%3Atransactional-workflows)
- [Browse Deploy web app](/v1/catalog/nodes/intent%3Adeploy-web-app)