Configure environment and secrets for Phoenix · Ample Computer

Configure environment and secrets for Phoenix

Configuration and secrets for a Phoenix app on Ample. Verified on Phoenix: an --env value delivered encrypted and reported as present without being echoed (secret=set). 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.

Verified November 6, 2026

What it runs on

You need

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. Pass values on deploy. Use --env KEY=value (repeatable) or --env-file; values are encrypted at rest and reused on redeploys. Declare names only in ample.toml.

   $ ample deploy . --name <app-name> --public --env MY_SECRET=...
  1. Verify. Fetch the live URL and /p/configuration-secrets 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”
✓ configuration-secrets check from the example · http get/p/configuration-secrets → “see the pattern fixture checks”

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); for this guide: an --env value delivered encrypted and reported as present without being echoed (secret=set).

Tested examples

What it doesn’t cover