## Host storefront with Phoenix: authorized file delivery

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

### Representative Queries
- Host storefront with Phoenix: authorized file delivery  
- Where can I host Storefront 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  
1. **Compute**  
   - Status: Verified  
   - Summary: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
 
2. **Postgres**  
   - Status: Verified  
   - Summary: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
 
3. **S3-compatible object storage**  
   - Status: Verified  
   - Summary: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

### Prerequisites
- A Phoenix project that builds and starts with the documented commands (mix deps.get, MIX_ENV=prod mix compile and mix release in the builder, then the release bin script with PHX_SERVER=true on the elixir-1.18 template; PORT, DATABASE_URL and SECRET_KEY_BASE read in config/runtime.exs)  
- 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

### Workflow Steps
1. **Build and start**  
   - mix deps.get, MIX_ENV=prod mix compile and mix release in the builder, then the release bin script with PHX_SERVER=true on the elixir-1.18 template; PORT, DATABASE_URL and SECRET_KEY_BASE read in config/runtime.exs. 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). 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/generated-downloads) from the example; then run your own checks. On failure read `ample logs  --kind build` then `--kind runtime`.  
   - Command: ample logs  --kind build

### Limitations
- Verified on the elixir-1.18 template at s-1vcpu-1gb with the example fixture; other sizes, templates and Phoenix major versions are not verified.  
- The storefront itself (your export formats, retention policy and entitlement model) is application code and was not separately tested; the pattern checks are what was verified.  
- Region, compliance attestations and request-duration limits are unknown and not claimed.  
- Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.  
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.  
- PutObject and GetObject with path-style addressing are verified; multipart upload, listing, presigned URLs and lifecycle rules are not.

### Cost Estimate
- **Currency**: USD  
- **Monthly Amount**: 10.0  
- **Note**: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

### Evidence Summary
- **Canary Run**: Phoenix pattern fixture deployed on Ample (mix deps.get, MIX_ENV=prod mix compile and mix release in the builder, then the release bin script with PHX_SERVER=true on the elixir-1.18 template; checks passed for generated-downloads and configuration-secrets).  
- **Observed At**: 2026-09-20T23:45:31Z

### Formats
- [HTML Version](/content/recipes/storefront/phoenix/download-delivery/index.html)  
- [Markdown Version](/content/recipes/storefront/phoenix/download-delivery.md)  
- [JSON Version](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Astorefront%3Aphoenix%3Adownload-delivery)