Connect Postgres for Phoenix · Ample Computer

Connect Postgres for Phoenix

Database connection for a Phoenix app on Ample. Verified on Phoenix: a managed PostgreSQL database auto-provisioned and injected as DATABASE_URL, with real queries succeeding at request time (records=ok). 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. Read DATABASE_URL at runtime. Open connections from the environment inside handlers or a pool; omit DATABASE_URL to auto-provision a managed database or pass --env DATABASE_URL=... for an existing one.

  3. Verify. Fetch the live URL and /p/relational-records 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”
✓ relational-records check from the example· http get/p/relational-records → “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: a managed PostgreSQL database auto-provisioned and injected as DATABASE_URL, with real queries succeeding at request time (records=ok).

Tested examples

What it doesn’t cover