page:recipes:order tracking:symfony:relational catalog

Host order tracking with Symfony: relational catalog data

Deploy an order tracking 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 order tracking-specific behavior as your application code.

Representative Queries

• Host order tracking with Symfony: relational catalog data
• Where can I host Order tracking built with Symfony?
• I need catalog tables, transactional update logic and application-level access boundaries.

Resource Requirements

• primitive:compute
• primitive:postgres

Infrastructure Requirements

1. Compute
   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
   Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

Pre-requisites

• 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)
• 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

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

Success Checks

• App responds on its public URL (http GET /)
• Transactional-workflows self-test (http GET /p/transactional-workflows)

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 order tracking 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)
  • Components:
    • App server: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 5.0
    • Managed PostgreSQL database: s-1vcpu-1gb, quantity: 1.0, monthlyAmount: 5.0
• Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

Format Links

• HTML: HTML Format
• Markdown: Markdown Format
• JSON: JSON Format

Next Actions

1. Browse the catalog index

   • Action ID: browse-catalog
   • Method: GET
   • Relative Path: /v1/catalog

2. Search published recipes by intent, stack, and constraints

   • Action ID: search-recipes
   • Method: POST
   • Relative Path: /v1/catalog/search
   • Parameters:
     • Body:

       {"limit":5,"query":"Host order tracking with Symfony: relational catalog data"}
       

3. Prepare a side-effect-free deployment plan for an authorized project

   • Action ID: plan:page:recipes:order-tracking:symfony:relational-catalog
   • Method: POST
   • Relative Path: /v1/catalog/plan
   • Parameters:
     • Body:

       {"inputs":{},"projectId":"","recipeId":"page:recipes:order-tracking:symfony:relational-catalog","recipeRevision":"r1"}
       

4. Read the existing agent authentication setup

   • Action ID: auth-setup
   • Method: GET
   • Relative Path: /mcp/setup

5. Browse Order tracking

   • Action ID: browse:workload:order-tracking
   • Method: GET
   • Relative Path: /v1/catalog/nodes/workload%3Aorder-tracking

6. Browse Symfony

   • Action ID: browse:stack:framework-symfony
   • Method: GET
   • Relative Path: /v1/catalog/nodes/stack%3Aframework-symfony

7. Browse Transactional workflows

   • Action ID: browse:pattern:transactional-workflows
   • Method: GET
   • Relative Path: /v1/catalog/nodes/pattern%3Atransactional-workflows

8. Browse Deploy web app

   • Action ID: browse:intent:deploy-web-app
   • Method: GET
   • Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app