Host order tracking with Symfony: authorized file delivery

Summary

Deploy a order tracking built with Symfony on Ample using the generated downloads 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. Verified on Symfony: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). Not separately tested: your export formats, retention policy and entitlement model; treat the order tracking-specific behavior as your application code.

Infrastructure requirements

• Verified Compute: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
• Verified 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.
• Verified S3-compatible object storage: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

Prerequisites

• 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).
• A PostgreSQL driver reading DATABASE_URL at runtime.
• A bucket from ample bucket create with its credentials passed as encrypted S3_* environment variables.
• An Ample account token with servers:write, databases:read, buckets:read.

Exact 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

Steps

1. Build and start. composer install --no-dev from composer.lock with Symfony Runtime's dotenv disabled. The server must bind 0.0.0.0 on PORT.
2. Implement the pattern on PostgreSQL. The fixture's module implements generated downloads: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3).
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 (exit 0 live, 1 failed, 2 blocked).

   ample deploy . --name <app-name> --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...

5. Verify. Fetch the live URL and the pattern self-test route(s) (/p/generated-downloads); then run your own checks.

Success checks

• App responds on its public URL (/ on the live URL, expect ample canary symfony patterns).
• Generated-downloads self-test (/p/generated-downloads on the live URL, expect export=ok rows=3).

Limitations

• Verified on the php-8.5 template; other sizes, templates and Symfony major versions are not verified.
• The order tracking itself (your export formats, retention policy and entitlement model) is application code and was not separately tested.
• Apps auto-pause when idle and wake on the next request.
• Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified.

Cost estimate

Estimated 10.00 USD per month.

Verification evidence

• Canary runs verified:
  • Symfony pattern fixture deployed on Ample; checks passed.

Execution binding

MCP tool ample_deploy, schema hash observed at revision.