page:guides:phoenix:build and start

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.

Workflow 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. Deploy
   Run the synchronous deploy once and read the result.
   Command: ample deploy . --name <your-app-name> --public

3. Verify
   Fetch the live URL on the example; on failure read the build and runtime logs.
   Command: ample logs <your-app-name> --kind build

Prerequisites

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

Success Checks

• App responds on its public URL via HTTP GET at /, expecting response from ample canary phoenix patterns.

Limitations

• Verified on the elixir-1.18 template at s-1vcpu-1gb; other sizes and Phoenix major versions are not verified.
• Region, compliance attestations and request-duration limits are unknown and not claimed.

Cost Estimate

• Currency: USD
• Monthly Amount: 5.0
• Basis: Size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
• Components:
  • App Server (Size: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: 5.0)
• Note: Always-on monthly price of the tested sizes; apps auto-pause when idle.

Examples

• Phoenix pattern fixture
  Verified build and start on Phoenix. Source Reference: tests/deploy-canaries/phoenix-patterns.

Evidence Summary

• Canary Run Summary:
  Phoenix pattern fixture deployed on Ample with documented build and start commands, responding on its public HTTPS URL.