# Host form collection with Laravel: relational workflow state

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

## Representative Queries
- Host form collection with Laravel: relational workflow state
- Where can I host Form collection built with Laravel?
- I need a domain record schema, validation rules and concurrency behavior.

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

## Infrastructure Requirements
### Compute
- **Label**: Compute  
- **Status**: verified  
- **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
- **Label**: Postgres  
- **Status**: verified  
- **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.

## 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.
   ```bash
   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`.
   ```bash
   ample logs  --kind build
   ```

## 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 form collection 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: size s-1vcpu-1gb, quantity 1.0, monthlyAmount 5.0  
   - managed PostgreSQL database: size s-1vcpu-1gb, quantity 1.0, monthlyAmount 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
- **Canary Run**: Laravel pattern fixture deployed on Ample; checks passed for transactional-workflows and configuration-secrets. Pattern proof: 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). Observed at: 2026-09-20T20: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  
3. **Prepare a side-effect-free deployment plan**: POST /v1/catalog/plan  
4. **Read the existing agent authentication setup**: GET /mcp/setup  
5. **Browse Form collection**: GET /v1/catalog/nodes/workload%3Aform-collection  
6. **Browse Laravel**: GET /v1/catalog/nodes/stack%3Aframework-laravel  
7. **Browse Transactional workflows**: GET /v1/catalog/nodes/pattern%3Atransactional-workflows  
8. **Browse Deploy web app**: GET /v1/catalog/nodes/intent%3Adeploy-web-app