## Host order tracking with Phoenix: public product media

### Summary
Deploy an order tracking 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 order tracking-specific behavior as your application code.

### Representative Queries
- Host order tracking with Phoenix: public product media
- Where can I host Order tracking 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

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

### Framework
Phoenix

### Workload
Order tracking

### Release Status
published

### Support Status
verified

### Execution Status
ready

### 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 (auto-provisioned when omitted, or supplied with --env)
- A bucket from `ample bucket create` with its credentials passed as encrypted S3_* environment variables and a second, published bucket for public assets (CDN_*)
- An Ample account token with servers:write, databases:read, buckets:read

### Tested Configuration
- **Template:** elixir-1.18
- **Runtime:** elixir
- **Size:** s-1vcpu-1gb
- **Install:** mix local.hex --force && mix local.rebar --force && MIX_ENV=prod mix deps.get --only prod
- **Build:** MIX_ENV=prod mix compile && MIX_ENV=prod mix release --overwrite
- **Start:** PHX_SERVER=true _build/prod/rel/$(ls _build/prod/rel | head -n 1)/bin/$(ls _build/prod/rel | head -n 1) start

### 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 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. 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. Publish only the bucket that serves public assets and reference its CDN URL.
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=... --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. On failure read `ample logs  --kind build` then `--kind runtime`.  
   **Command:** ample logs  --kind build

### Success Checks
- App responds on its public URL with a check for ample canary phoenix patterns.
- Public-media-library self-test for a CDN URL whose content is served publicly.

### 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 order tracking itself (your media processing, object layout and cache policy) 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.
- The CDN serves published-bucket objects only; cache rules, purge and TTL control are not verified (the fixture sets Cache-Control on upload and versions keys).

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

| Name                              | Size           | Quantity | Monthly Amount |
|-----------------------------------|----------------|----------|----------------|
| app server                        | s-1vcpu-1gb    | 1.0      | 5.0            |
| managed PostgreSQL database       | s-1vcpu-1gb    | 1.0      | 5.0            |

### 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; PORT, DATABASE_URL and SECRET_KEY_BASE read in config/runtime.exs); checks passed for public-media-library and configuration-secrets. Pattern proof: an object written to a published bucket with an immutable Cache-Control header, a mapping row, and the CDN URL serving it publicly.  
**Observed At:** 2026-09-20T23:45:31Z
**Implementation Revision:** 4d1511e574302f3904b75088bd4048a0975218b3-dirty (CLI 0.1.21)
**Expires At:** 2027-03-19T23:45:31Z

- **Canary Run:**  
  The same Phoenix app deployed with a --release-command migration; the marker it created was readable after activation.  
**Observed At:** 2026-09-20T23:45:31Z
**Implementation Revision:** 4d1511e574302f3904b75088bd4048a0975218b3-dirty (CLI 0.1.21)
**Expires At:** 2027-03-19T23:45:31Z

### Next Actions
1. **Browse the catalog index**  
   **Operation ID:** catalog_index  
   **Method:** GET  
   **Relative Path:** /v1/catalog
2. **Search published recipes by intent, stack and constraints**  
   **Operation ID:** search_recipes  
   **Method:** POST  
   **Parameters:**  
   - body:{
       limit: 5,
       query: "Host order tracking with Phoenix: public product media"
   }
   **Relative Path:** /v1/catalog/search
3. **Prepare a side-effect-free deployment plan for an authorized project**  
   **Operation ID:** plan_deployment  
   **Method:** POST  
   **Parameters:**  
   - Inputs:{
       projectId: "",
       recipeId: "page:recipes:order-tracking:phoenix:product-media",
       recipeRevision: "r1"
   }
   **Relative Path:** /v1/catalog/plan
4. **Read the existing agent authentication setup**  
   **Operation ID:** existing_auth_setup  
   **Method:** GET  
   **Relative Path:** /mcp/setup
5. **Browse Order tracking**  
   **Operation ID:** browse_node  
   **Method:** GET  
   **Parameters:**  
   - nodeId: workload:order-tracking
   **Relative Path:** /v1/catalog/nodes/workload%3Aorder-tracking