page:recipes:order tracking:symfony:product media

Host Order Tracking with Symfony: Public Product Media

Summary

Deploy an order tracking built with Symfony on Ample using the public media library 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, a private S3-compatible bucket holds objects with credentials delivered as encrypted environment variables, and a published bucket serves public assets from the CDN host. Verified on Symfony: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly. Not separately tested: your media processing, object layout, and cache policy; treat the order tracking-specific behavior as your application code.

Representative Queries

• Host order tracking with Symfony: public product media
• Where can I host Order tracking built with Symfony?
• I need product-to-object mappings and a tested public media delivery path.

Resource Requirements

• primitive:compute
• primitive:postgres
• primitive:s3-compatible-object-storage
• primitive:cdn

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.
• S3-Compatible Object Storage: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.
• CDN: The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.

Workflow Steps

1. Build and Start: composer install --no-dev from composer.lock with Symfony Runtime's dotenv disabled. Then run 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 public media library: an object written to a published bucket with an immutable Cache-Control header. Copy the approach into your schema; keep migrations idempotent and run them with --release-command.
3. Wire Object Storage: Create the bucket(s), then pass endpoint, region, bucket and keys as --env values. Use path-style addressing. Keep private data in an unpublished bucket.
4. Deploy: Run the synchronous deploy once and read the result. Re-running with no change is a no-op. Command: ample deploy . --name --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=... --env CDN_PUBLIC_URL=...
5. Verify: Fetch the live URL and the pattern self-test route(s) (/p/public-media-library) from the example; then run your own checks. Command: ample logs --kind build

Success Checks

• App responds on its public URL.
• Public-media-library self-test.

Limitations

• Verified on the php-8.5 template at s-1vcpu-1gb with the example fixture; other sizes, templates and Symfony versions are not verified.
• The order tracking itself is application code and was not separately tested.

Cost Estimate

• Monthly Amount: 10.0 USD
• Components:
  • App server: s-1vcpu-1gb, quantity: 1, monthly amount: 5.0 USD
  • Managed PostgreSQL database: s-1vcpu-1gb, quantity: 1, monthly amount: 5.0 USD

Next Actions

• Browse the catalog index
• Search published recipes by intent, stack and constraints
• Prepare a deployment plan for an authorized project
• Read the existing agent authentication setup

Evidence Summary

• Symphony pattern fixture deployed on Ample. Checks passed for public-media-library and configuration-secrets.
• The same Symfony app deployed with a release-command migration; the marker it created was readable after activation.