## Host marketplace with Laravel: relational catalog data

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

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

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

### Infrastructure Requirements
- **Compute**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
- **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.

### Framework
Laravel  
### Workload
Marketplace

### Release Status
Published  
### Support Status
Verified  
### Execution Status
Ready

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

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

### Examples
- **Laravel pattern fixture**: Multi-pattern Laravel app whose transactional workflows module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

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

### 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 marketplace 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
- **Basis**: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty

### 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 for an authorized project**: POST /v1/catalog/plan
4. **Read the existing agent authentication setup**: GET /mcp/setup
5. **Browse Marketplace**: GET /v1/catalog/nodes/workload%3Amarketplace
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

--- 
This content is related to hosting a marketplace built with Laravel and includes various aspects related to its deployment, requirements, limitations, and cost estimates.