## Host marketplace with Symfony: relational catalog data

Deploy a marketplace built with Symfony 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 Symfony: 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 Symfony: relational catalog data
- Where can I host Marketplace built with Symfony?
- I need catalog tables, transactional update logic and application-level access boundaries.

### Resource Requirements
- Compute
- PostgreSQL

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

### Workload
Marketplace

### Release Status
Published

### Support Status
Verified

### Execution Status
Ready

### Prerequisites
1. A Symfony project that builds and starts with the documented commands (`composer install --no-dev` from `composer.lock` with Symfony Runtime's dotenv disabled). 
2. A PostgreSQL driver reading DATABASE_URL at runtime.
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**: `composer install --no-dev`... The server must bind 0.0.0.0 on PORT.

2. **Implement the pattern on PostgreSQL**: 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.

4. **Verify**: Fetch the live URL and run your own checks.

### Examples
- **Symfony pattern fixture**: Multi-pattern Symfony app whose transactional workflows module was checked live.

### Success Checks
1. App responds on its public URL.
2. Transactional-workflows self-test.

### Limitations
- Verified on the php-8.5 template at s-1vcpu-1gb. Other sizes, templates, and Symfony major versions are not verified.

### Cost Estimate
- **Currency**: USD
- **Monthly Amount**: $10.00
- **Components**:
  - App server: s-1vcpu-1gb, 1.0 quantity, $5.00 monthly
  - Managed PostgreSQL database: s-1vcpu-1gb, 1.0 quantity, $5.00 monthly

### Evidence Summary
- **Orchestrated deployment**: Symfony pattern fixture deployed on Ample, checks passed for transactional workflows and configuration secrets.

### Unknowns
- Region availability and compliance attestations are unknown.

### Formats
- [HTML format](/content/recipes/marketplace/symfony/relational-catalog/index.html)
- [Markdown format](/content/recipes/marketplace/symfony/relational-catalog.md)
- [JSON format](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Amarketplace%3Asymfony%3Arelational-catalog)