# Host recruiting tracker with Phoenix: relational workspace data

Deploy a recruiting tracker built with Phoenix on Ample using the relational records 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: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). The recruiting tracker-specific behavior (your record schema, states and access rules) is your application code on that verified basis.

Verified November 6, 2026

## What it runs on

- [Computeverified](/content/discover/primitive/compute/index.html)
  Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

- [Postgresverified](/content/discover/primitive/postgres/index.html)
  Managed PostgreSQL 16 with pgvector runs in its own microVM and is auto-provisioned when an app needs a database and no `DATABASE_URL` is supplied.

## You need

- 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)
- A PostgreSQL driver reading `DATABASE_URL` at runtime (auto-provisioned when omitted, or supplied with --env)
- An Ample account token with `servers:write`, `databases:read`

## 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 relational records: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true). 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/relational-records`) from the example; then run your own checks. On failure read `ample logs <deployment_id> --kind build` then `--kind runtime`.

```
   $ ample logs <deployment_id> --kind build
   ```

## How it was checked

✓ app responds on its public URL· `http get/` → “ample canary phoenix patterns”  
✓ relational-records self-test· `http get/p/relational-records` → “records=ok transitions=true isolation=true”

## 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 relational-records and configuration-secrets. Pattern proof: a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true).

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 relational records 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 recruiting tracker itself (your record schema, states and access rules) is your application code.
- Managed PostgreSQL 16 with pgvector; apps and their databases are placed together.
