### Host product catalog with Phoenix: authorized file delivery

Deploy a product catalog built with Phoenix 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 Phoenix: 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 product catalog-specific behavior as your application code.

#### Representative Queries
- Host product catalog with Phoenix: authorized file delivery
- Where can I host Product catalog built with Phoenix?
- I need a file entitlement model and an application-enforced download authorization flow.

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

#### 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.

#### Workflow Steps
1. **Build and start**: `mix deps.get`, `MIX_ENV=prod mix compile` and `mix release` in the builder. The server must bind `0.0.0.0` on PORT.
2. **Implement the pattern on PostgreSQL**: 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.
4. **Deploy**: Run the synchronous deploy once and read the result. Re-running with no change is a no-op. 
5. **Verify**: Fetch the live URL and check routes. On failure read `ample logs  --kind build` then `--kind runtime`.

#### Examples
- **Phoenix pattern fixture**: Multi-pattern Phoenix app whose generated downloads module was checked live.

#### Success Checks
- App responds on its public URL: `ample canary phoenix patterns`
- Generated-downloads self-test: export=ok rows=3 (with ?token=...; 401 without)

#### Limitations
- Verified on the elixir-1.18 template at s-1vcpu-1gb; other sizes, templates and Phoenix major versions are not verified.
- The product catalog itself (your export formats, retention policy and entitlement model) is application code.

#### Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Components**:
  - App server: monthlyAmount 5.0
  - Managed PostgreSQL database: monthlyAmount 5.0

#### Evidence Summary
- **Canary run**: Phoenix pattern fixture deployed on Ample, checks passed for generated-downloads and configuration-secrets.

#### Formats
- **HTML**: [Host product catalog with Phoenix](/content/recipes/product-catalog/phoenix/download-delivery/index.html)
- **Markdown**: [Host product catalog with Phoenix (Markdown)](/content/recipes/product-catalog/phoenix/download-delivery.md)
- **JSON**: [Host product catalog with Phoenix (JSON)](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Aproduct-catalog%3Aphoenix%3Adownload-delivery)