page:recipes:community forum:phoenix:activity history

Host community forum with Phoenix: application activity history

Deploy a community forum 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). Not separately tested: your domain records, validation rules and concurrency policy; treat the community forum-specific behavior as your application code.

Representative Queries

Resource Requirements

Infrastructure Requirements

Prerequisites

  1. A Phoenix project that builds and starts with the documented commands (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).
  2. A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env).
  3. An Ample account token with servers:write, databases:read.

Tested Configuration

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...
  2. Implement the pattern on PostgreSQL: The fixture's module implements transactional workflows...
  3. Deploy: Run the synchronous deploy once and read the result...
  4. Verify: Fetch the live URL...

Examples

Success Checks

Limitations

Cost Estimate

Evidence Summary

Last Verified At

2026-09-20T23:45:31Z

Unknowns

Formats

Next Actions