product media.md

Host subscription content with Symfony: public product media

Summary

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

Infrastructure requirements

Prerequisites

Exact tested configuration

Steps

  1. Build and start. composer install --no-dev from composer.lock with Symfony Runtime's dotenv disabled, then FrankenPHP serving public/ 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; 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. Publish only the bucket that serves public assets and reference its CDN URL.
  4. 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.
  5. Verify. Fetch the live URL and the pattern self-test route(s); then run your own checks. On failure read ample logs <deployment_id> --kind build then --kind runtime.

Tested examples

Success checks

Limitations

Cost estimate

Estimated 10.00 USD per month:

Verification evidence

Execution binding

MCP tool ample_deploy, schema hash observed 2026-09-21T03:19:59.461917+00:00.