## Host storefront with Symfony: inventory imports

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

### Representative Queries
- Host storefront with Symfony: inventory imports
- Where can I host Storefront built with Symfony?
- I need an inventory import contract, staging objects and row-level error handling.

### Resource Requirements
- primitive:compute
- primitive:postgres
- primitive:s3-compatible-object-storage

### Supported Framework
**Symfony**

### Workload
**Storefront**

### 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 (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 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 (imported=2 rejected=1 restart=ok). 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 (exit 0 live, 1 failed, 2 blocked). 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=...`

5. **Verify**
   - Fetch the live URL and the pattern self-test route(s) (/p/bulk-import-staging) 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
- Bulk-import-staging self-test

### 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 storefront itself (your import format, mapping and conflict rules) is application code and was not separately tested; the pattern checks are what was verified.

### Examples
- **Symfony pattern fixture**
  - Multi-pattern Symfony app whose bulk import staging module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
  - Source Reference: tests/deploy-canaries/symfony-patterns

### Cost Estimate
- Estimated cost: $10.00/month.
- Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

### Evidence Summary
- Symfony pattern fixture deployed on Ample; checks passed for bulk-import-staging and configuration-secrets. 
- **Last verified** at 2026-09-20T22:23:52Z.