## The short version

Deploy a company website 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.

---

## WHAT WAS VERIFIED

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.

---

## INFRASTRUCTURE

### What it needs

- [Compute](/content/discover/primitive/compute/index.html): verified (Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.)
- [Postgres](/content/discover/primitive/postgres/index.html): 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.)
- [S3-compatible object storage](/content/discover/primitive/s3-compatible-object-storage/index.html): verified (Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.)
- [CDN](/content/discover/primitive/cdn/index.html): verified (A published bucket's objects are served at its `public_url`. It does not front app compute and is not a cache or key-value store.)

---

## PREREQUISITES

### Before you start

- 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`

---

## STEP BY STEP

### How to do it

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.  
    
    ```
    ample deploy . --name <app-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 <deployment_id> --kind build` then `--kind runtime`.  
    
    ```
    ample logs <deployment_id> --kind build
    ```

---

## EXAMPLES

### Tested examples

- **Phoenix pattern fixture** (`tests/deploy-canaries/phoenix-patterns`): Multi-pattern Phoenix app whose public media library module was checked live; the module is under `tests/deploy-canaries/_pattern-modules`.

---

## SUCCESS CHECKS

### How to know it worked

- App responds on its public URL (`/` on the live URL, expect ample canary phoenix patterns)
- public-media-library self-test (`/p/public-media-library` on the live URL, expect a CDN URL whose content is served publicly)

---

## COST

### Cost estimate

Estimated **10.00 USD** per month (size prices from `pricing.toml` at build revision `ca0b484a7a9957c573a88d3a32dc603c3c10135a`).

- App server x1 `s-1vcpu-1gb`: **5.00 USD**
- Managed PostgreSQL database x1 `s-1vcpu-1gb`: **5.00 USD**

Upper-bound monthly price of the tested sizes. Buckets are allocation-priced per quota and not included.

---

## EVIDENCE

### Verification evidence

- **canary_run** on 2026-09-20T23:45:31Z at revision `4d1511e574302f3904b75088bd4048a0975218b3 (CLI 0.1.21)`: 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. (expires 2027-03-19T23:45:31Z)
- **canary_run** on 2026-09-20T23:45:31Z at revision `4d1511e574302f3904b75088bd4048a0975218b3 (CLI 0.1.21)`: The same Phoenix app deployed with a `--release-command` migration; the marker it created was readable after activation. (expires 2027-03-19T23:45:31Z)

---

## EXECUTION

### Execution binding

MCP tool `ample_deploy` (registry `mcp:ample_deploy`), schema hash `876465fce906da0c` observed 2026-09-22T00:31:22.774679+00:00 at revision `e6446ceea69b`. Binding state at export: schema_changed. Required scopes: `servers:write`, `databases:read`, `buckets:read`.