# 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

- [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.

## 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 PostgreSQL driver reading DATABASE\_URL at runtime
- An Ample account token with servers:write, databases: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. **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

- **Phoenix pattern fixture.** Verified database connection on Phoenix.

## What it doesn’t cover

- Verified on the elixir-1.18 template at s-1vcpu-1gb.
- Managed PostgreSQL 16 with pgvector.
