# Host blog with Phoenix: object-stored public media

Deploy a blog 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. The blog-specific behavior (your media processing, object layout and cache policy) is your application code on that verified basis.

## What it runs on

- [Computeverified](/content/discover/primitive/compute/index.html)  
  Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

- [Postgresverified](/content/discover/primitive/postgres/index.html)  
  Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no `DATABASE_URL` is supplied.

- [S3-compatible object storageverified](/content/discover/primitive/s3-compatible-object-storage/index.html)  
  Buckets speak the S3 API with SigV4 credentials Ample Computer issues; `ample bucket upload-url` returns a presigned upload URL. PutObject and GetObject are checked by canary.

- [CDNverified](/content/discover/primitive/cdn/index.html)  
  A published bucket's objects are served from its public URL; set Cache-Control when uploading to control caching. App responses are served by the app.

## You need

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

## Exact tested configuration

- build  
  `MIX_ENV=prod mix compile && MIX_ENV=prod mix release --overwrite`

- install  
  `mix local.hex --force && mix local.rebar --force && MIX_ENV=prod mix deps.get --only prod`

- runtime  
  elixir

- sizes  
  1vcpu-1gb

- start  
  `PHX_SERVER=true _build/prod/rel/$(ls _build/prod/rel | head -n 1)/bin/$(ls _build/prod/rel | head -n 1) start`

- template  
  elixir-1.18

## 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 needs an answer first). 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
   ```

## How it was checked

- ✓ app responds on its public URL · `http get/` → "ample canary phoenix patterns"
- ✓ public-media-library self-test · `http get/p/public-media-library` → "a CDN URL whose content is served publicly"

## Evidence

1. November 6, 2026 · 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.

2. November 6, 2026 · canary run  
   The same Phoenix app deployed with a `--release-command` migration; the marker it created was readable after activation.

## Tested examples

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

## What it doesn’t cover

- Verified on the elixir-1.18 template at s-1vcpu-1gb with the example fixture.
- The pattern checks verified the platform side; the blog itself (your media processing, object layout and cache policy) is your application code.
- Managed PostgreSQL 16 with pgvector; apps and their databases are placed together.
- Buckets speak the standard S3 API (PutObject and GetObject with path-style addressing are checked by the fixture); `ample bucket upload-url` returns presigned upload URLs.
- The CDN serves published-bucket objects; control caching with Cache-Control on upload and versioned keys.
