# Host subscription content with Symfony: relational catalog data

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

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

## Resource Requirements
- Compute
- PostgreSQL

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

2. **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.

## Framework
Symfony

## Workload
Subscription content

## 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 (extra.runtime.disable_dotenv; .env never ships, its values arrive as encrypted env, and compile-time parameters such as DEFAULT_URI need a default), then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 template with APP_ENV=prod)
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**  
   composer install --no-dev from composer.lock with Symfony Runtime's dotenv disabled (extra.runtime.disable_dotenv; .env never ships, its values arrive as encrypted env, and compile-time parameters such as DEFAULT_URI need a default), then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 template with APP_ENV=prod. 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
### Symfony pattern fixture
- **Description**: Multi-pattern Symfony app whose transactional workflows module was checked live; the module is under tests/deploy-canaries/_pattern-modules.  
- **Source Reference**: tests/deploy-canaries/symfony-patterns

## Success Checks
1. **App responds on its public URL**  
   - Kind: http_get  
   - Path: /  
   - Expect: ample canary symfony 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 Symfony major versions are not verified.
- The subscription content 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**:
  - **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  
- **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
- **Kind**: canary_run  
  - **Summary**: Symfony pattern fixture deployed on Ample; checks passed for transactional-workflows and configuration-secrets.
  - **Observed At**: 2026-09-20T22:23:52Z  
  - **Implementation Revision**: 64a7bb8e37dd-dirty (CLI 64a7bb8)  
  - **Expires At**: 2027-03-19T22:23:52Z

## Last Verified At
2026-09-20T22:23:52Z

## Unknowns
- Region availability is unknown until a verified region fact is recorded.
- Compliance attestations are unknown; none are claimed.