Host client portal with Phoenix: application activity history · Ample Computer
Host client portal with Phoenix: application activity history
Deploy a client portal built with Phoenix on Ample using the transactional workflows pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, a managed PostgreSQL 16 database is auto-provisioned and injected as DATABASE_URL. Verified on Phoenix: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected). The client portal-specific behavior (your domain records, validation rules and concurrency policy) is your application code on that verified basis.
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 noDATABASE_URLis supplied.
You need
A Phoenix project that builds and starts with the documented commands (mix deps.get,
MIX_ENV=prod mix compileandmix releasein the builder, then the release bin script withPHX_SERVER=trueon the elixir-1.18 template; PORT,DATABASE_URLandSECRET_KEY_BASEread inconfig/runtime.exs)A PostgreSQL driver reading
DATABASE_URLat runtime (auto-provisioned when omitted, or supplied with--env)An Ample account token with
servers:write,databases:read
Exact tested configuration
buildMIX_ENV=prod mix compile && MIX_ENV=prod mix release --overwriteinstallmix local.hex --force && mix local.rebar --force && MIX_ENV=prod mix deps.get --only prodruntimeelixirsizes1vcpu-1gbstartPHX_SERVER=true _build/prod/rel/$(ls _build/prod/rel | head -n 1)/bin/$(ls _build/prod/rel | head -n 1) starttemplateelixir-1.18
Steps
Build and start.
mix deps.get,MIX_ENV=prod mix compileandmix releasein the builder, then the release bin script withPHX_SERVER=trueon the elixir-1.18 template; PORT,DATABASE_URLandSECRET_KEY_BASEread inconfig/runtime.exs. The server must bind0.0.0.0on PORT.Implement the pattern on PostgreSQL. The fixture's module implements transactional workflows: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (
history=2 conflict=rejected). Copy the approach into your schema; keep migrations idempotent and run them with--release-command.Deploy. Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 needs an answer first). Re-running with no change is a no-op.
$ ample deploy . --name <app-name> --public
- Verify. Fetch the live URL and the pattern self-test route(s) (
/p/transactional-workflows) from the example; then run your own checks. On failure readample logs <deployment_id> --kind buildthen--kind runtime.
$ ample logs <deployment_id> --kind build
How it was checked
✓ app responds on its public URL · http get/ → "ample canary phoenix patterns"
✓ transactional-workflows self-test · http get/p/transactional-workflows → "tx=ok history=2 conflict=rejected"
Evidence
November 6, 2026 · canary run
Phoenix pattern fixture deployed on Ample (mix deps.get,MIX_ENV=prod mix compileandmix releasein the builder, then the release bin script withPHX_SERVER=trueon the elixir-1.18 template; PORT,DATABASE_URLandSECRET_KEY_BASEread inconfig/runtime.exs); checks passed for transactional-workflows and configuration-secrets. Pattern proof: an optimistic version check and an event row written in the same transaction, a stale update rejected, and a history query over the application-owned events (history=2 conflict=rejected).November 6, 2026 · canary run
The same Phoenix app deployed with a--release-commandmigration; the marker it created was readable after activation.
Tested examples
- Phoenix pattern fixture. Multi-pattern Phoenix app whose transactional workflows module was checked live; the module is under
tests/deploy-canaries/_pattern-modules.
What it doesn’t cover
- Verified on the elixir-1.18 template at s-1vcpu-1gb with the example fixture.
- The pattern checks verified the platform side; the client portal itself (your domain records, validation rules and concurrency policy) is your application code.
- Managed PostgreSQL 16 with pgvector; apps and their databases are placed together.