page:recipes:digital downloads:symfony:inventory imports

Host digital downloads with Symfony: inventory imports

Summary

Deploy a digital downloads built with Symfony on Ample using the bulk import staging 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: a CSV staged as an object, row-level validation with per-row errors recorded, and a restart-safe import keyed by import id (imported=2 rejected=1 restart=ok). Not separately tested: your import format, mapping and conflict rules; treat the digital downloads-specific behavior as your application code.

Resource Requirements

Framework

Symfony

Workload

Digital downloads

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. A bucket from ample bucket create with its credentials passed as encrypted S3_* environment variables
  4. An Ample account token with servers:write, databases:read, buckets:read

Workflow Steps

  1. Build and start
    composer install --no-dev from composer.lock with Symfony Runtime's dotenv disabled, then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 template with APP_ENV=prod.

  2. Implement the pattern on PostgreSQL
    The fixture's module implements bulk import staging: a CSV staged as an object, row-level validation with per-row errors recorded, and a restart-safe import keyed by import id.

  3. Wire object storage
    Create the bucket(s), then pass endpoint, region, bucket and keys as --env values. Use path-style addressing.

  4. Deploy
    Run the synchronous deploy once and read the result.

    ample deploy . --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); then run your own checks.

    ample logs --kind build
    

Examples

Success Checks

  1. App responds on its public URL.
  2. Bulk-import-staging self-test.

Limitations

Cost Estimate

Evidence Summary

  1. Canary Run: Symfony pattern fixture deployed on Ample.
    • Observed At: 2026-09-20
    • Summary: Checks passed for bulk-import-staging and configuration-secrets.

Formats

Next Actions