Apply database schema changes for Phoenix · Ample Computer
Apply database schema changes for Phoenix
Schema changes for a Phoenix app on Ample. Verified on Phoenix: a --release-command migration ran before activation and its marker was readable by the live app (migrated=release-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.
What it runs on
Computeverified
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.Postgresverified
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
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.
Run migrations as the release command. Ample runs the command before activation and fails the release if it exits non-zero; keep migrations idempotent.
$ ample deploy . --name <app-name> --public --release-command "python3 migrate.py"
- Verify. Fetch the live URL and /p/migrated 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”
✓migrated check from the example· http get/p/migrated → “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 --release-command migration ran before activation and its marker was readable by the live app (migrated=release-ok).
Tested examples
- Phoenix pattern fixture. Verified schema changes on Phoenix.
What it doesn’t cover
- Verified on the elixir-1.18 template at s-1vcpu-1gb.
- Managed PostgreSQL 16 with pgvector.