# Host Reporting Dashboard with Laravel: Relational Workflow State

## Summary
Deploy a reporting 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 reporting dashboard-specific behavior as your application code.

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

## 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 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.
   - **Command**: 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`.
   - **Command**: ample logs  --kind build

## Examples
- **Laravel pattern fixture**: Multi-pattern Laravel app whose transactional workflows 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 reporting 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.
- 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.

## Success Checks
1. **App responds on its public URL**: kind: http_get, path: /, expect: ample canary laravel patterns
2. **Transactional-workflows self-test**: kind: http_get, path: /p/transactional-workflows, expect: tx=ok history=2 conflict=rejected

## Evidence Summary
1. **Canary Run**: 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 transactional-workflows and configuration-secrets. 
   - **Observed At**: 2026-09-20T20:36:21Z

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

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