# Host asset library with Laravel: relational workflow state

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

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

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

## Infrastructure Requirements  
1. **Compute**  
   - **Summary**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.  
   - **Status**: verified  
   - **Canonical Path**: /discover/primitive/compute

2. **Postgres**  
   - **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.  
   - **Status**: verified  
   - **Canonical Path**: /discover/primitive/postgres

## Framework  
Laravel

## Workload  
Asset library

## Release Status  
Published

## Support Status  
Verified

## 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)  
- 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  
- **Title**: Laravel pattern fixture  
   - **Description**: Multi-pattern Laravel app whose transactional workflows module was checked live; the module is under tests/deploy-canaries/_pattern-modules.  
   - **Source Reference**: tests/deploy-canaries/laravel-patterns

## Success Checks  
1. **Description**: app responds on its public URL  
   - **Kind**: http_get  
   - **Path**: /  
   - **Expect**: ample canary laravel patterns

2. **Description**: transactional-workflows self-test  
   - **Kind**: http_get  
   - **Path**: /p/transactional-workflows  
   - **Expect**: tx=ok history=2 conflict=rejected

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

## Cost Estimate  
- **Currency**: USD  
- **Monthly Amount**: 10.0  
- **Authoritative**: true  
- **Basis**: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty  
- **Components**:  
  - **Name**: app server  
    - **Size**: s-1vcpu-1gb  
    - **Quantity**: 1.0  
    - **Monthly Amount**: 5.0  
  - **Name**: 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.