Deliver public assets through CDN for Phoenix · Ample Computer
Deliver public assets through CDN for Phoenix
Cdn assets for a Phoenix app on Ample. Verified on Phoenix: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL. 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.
What it runs on
- Computeverified
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes. - CDNverified
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 (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 bucket from
ample bucket createwith credentials passed as encrypted S3_* environment variables - An Ample account token with servers:write, buckets:read
Exact tested configuration
buildMIX_ENV=prod mix compile && MIX_ENV=prod mix release --overwrite
installmix local.hex --force && mix local.rebar --force && MIX_ENV=prod mix deps.get --only prod
runtimeelixir
sizes-1vcpu-1gb
startPHX_SERVER=true _build/prod/rel/$(ls _build/prod/rel | head -n 1)/bin/$(ls _build/prod/rel | head -n 1) start
templateelixir-1.18
Steps
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.
Publish a bucket for public assets. Publish only the asset bucket; upload versioned keys with an immutable Cache-Control header and build URLs from its public URL.
$ ample bucket publish <bucket-name>Verify. Fetch the live URL and /p/versioned-static-assets on the example; on failure read the build and runtime logs.
$ ample logs <deployment_id> --kind build
How it was checked
✓app responds on its public URL· http get/ → “ample canary phoenix patterns”
✓versioned-static-assets check from the example· http get/p/versioned-static-assets → “see the pattern fixture checks”
Evidence
- 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); for this guide: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL.
Tested examples
- Phoenix pattern fixture. Verified CDN assets on Phoenix.
What it doesn’t cover
- Verified on the elixir-1.18 template at s-1vcpu-1gb.
- The CDN serves published-bucket objects; control caching with Cache-Control on upload and versioned keys.