# Host product catalog with Laravel: relational catalog data

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

## Representative Queries
- Host product catalog with Laravel: relational catalog data
- Where can I host Product catalog built with Laravel?
- I need catalog tables, transactional update logic and application-level access boundaries.

## Resource Requirements
- **Compute**
- **Postgres**

## Infrastructure Requirements
- **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**  
  - 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
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

## 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**  
   Command: 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**  
   - Command: ample deploy . --name --public  
   - 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.  
4. **Verify**  
   - Command: ample logs --kind build  
   - 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`.

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

## Success Checks
- App responds on its public URL
  - **Kind**: http_get  
  - **Path**: /  
  - **Expect**: ample canary laravel patterns  
- 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 product catalog 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  
- **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.
  - **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

## Next Actions
- **Browse the catalog index**  
  - Action ID: browse-catalog  
- **Search published recipes by intent, stack and constraints**  
  - Action ID: search-recipes  
- **Prepare a side-effect-free deployment plan for an authorized project**  
  - Action ID: plan:page:recipes:product-catalog:laravel:relational-catalog  
- **Read the existing agent authentication setup**  
  - Action ID: auth-setup  
- **Browse Product catalog**  
  - Action ID: browse:workload:product-catalog  
- **Browse Laravel**  
  - Action ID: browse:stack:framework-laravel  
- **Browse Transactional workflows**  
  - Action ID: browse:pattern:transactional-workflows  
- **Browse Deploy web app**  
  - Action ID: browse:intent:deploy-web-app