# Host product catalog with Phoenix: public product media

Deploy a product catalog built with Phoenix on Ample using the public media library 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, and a published bucket serves public assets from the CDN host. Verified on Phoenix: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly. Not separately tested: your media processing, object layout and cache policy; treat the product catalog-specific behavior as your application code.

## Representative Queries
- Host product catalog with Phoenix: public product media
- Where can I host Product catalog built with Phoenix?
- I need product-to-object mappings and a tested public media delivery path.

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

## Infrastructure Requirements
1. **Compute**
   - Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
2. **Postgres**
   - Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
3. **S3-compatible object storage**
   - Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.
4. **CDN**
   - The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.

## 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.`
2. **Implement the pattern on PostgreSQL**  
   `The fixture's module implements public media library: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly.`
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 (exit 0 live, 1 failed, 2 blocked).`  
   - Command: `ample deploy . --name --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=... --env CDN_PUBLIC_URL=...`
5. **Verify**  
   `Fetch the live URL and the pattern self-test route(s) (/p/public-media-library) from the example; then run your own checks.`

## 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 product catalog itself (your media processing, object layout and cache policy) is application code and was not separately tested; the pattern checks are what was verified.

## Example
- **Phoenix pattern fixture**  
  Multi-pattern Phoenix app whose public media library module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

## Success Checks
1. **App responds on its public URL**  
   Path: `/`, Expect: `ample canary phoenix patterns`
2. **Public-media-library self-test**  
   Path: `/p/public-media-library`, Expect: `a CDN URL whose content is served publicly`.

## Cost Estimate
- Monthly Amount: `$10.0`
- Components:
  - App server: size s-1vcpu-1gb, quantity 1.0, monthly amount $5.0
  - Managed PostgreSQL database: size s-1vcpu-1gb, quantity 1.0, monthly amount $5.0
  - Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

## Next Actions
1. **Browse the catalog index**  
   - Operation ID: `catalog_index`, Method: `GET`, Relative Path: `/v1/catalog`
2. **Prepare a side-effect-free deployment plan for an authorized project**  
   - Operation ID: `plan_deployment`, Method: `POST`, Relative Path: `/v1/catalog/plan`