Configure build and start for Phoenix · Ample Computer
Configure build and start for Phoenix
Build and start for a Phoenix app on Ample. Verified on Phoenix: the app built and started with the documented commands and answered on its public HTTPS 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.
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)
- An Ample account token with servers:write
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
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.
Deploy. Run the synchronous deploy once and read the result.
$ ample deploy . --name <app-name> --public
```
3. **Verify.** Fetch the live URL on the example; on failure read the build and runtime logs.
```sh
$ ample logs <deployment_id> --kind build
```
## How it was checked
✓ app responds on its public URL · http get/ → “ample canary phoenix patterns”
## 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: the app built and started with the documented commands and answered on its public HTTPS URL.
## Tested examples
- **Phoenix pattern fixture.** Verified build and start on Phoenix.
## What it doesn’t cover
- Verified on the elixir-1.18 template at s-1vcpu-1gb.