Host community forum with Phoenix: application activity history · Ample Computer

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). The community forum-specific behavior (your domain records, validation rules and concurrency policy) is your application code on that verified basis.

Verified November 6, 2026

What it runs on

You need

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

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

  3. 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
    ```

4. **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 read `ample logs <deployment_id> --kind build` then `--kind runtime`.

```bash
    $ 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

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`); 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`).

2. November 6, 2026 · canary run
   The same Phoenix app deployed with a `--release-command` migration; 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 community forum 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.