## 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, and 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). Not separately tested: your record schema, states and access rules; treat the recruiting tracker-specific behavior as your application code.

### Representative Queries
- Host recruiting tracker with Phoenix: relational workspace data
- Where can I host Recruiting tracker built with Phoenix?
- I need a workspace-specific schema, state transitions, and access rules.

### Resource Requirements
- primitive:compute
- primitive:postgres

### Infrastructure Requirements
1. **Compute**  
   - Status: verified  
   - Summary: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.  
   - [More info](/discover/primitive/compute)

2. **Postgres**  
   - Status: verified  
   - Summary: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.  
   - [More info](/discover/primitive/postgres)

### Prerequisites
- 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

### 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. **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 blocked). Re-running with no change is a no-op.  
   - Command: ample deploy . --name <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`.  
   - Command: ample logs --kind build

### Examples
- **Phoenix pattern fixture**  
  - Multi-pattern Phoenix app whose relational records module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

### Success Checks
1. App responds on its public URL
   - Kind: http_get  
   - Path: /  
   - Expect: ample canary phoenix patterns

2. Relational-records self-test
   - Kind: http_get  
   - Path: /p/relational-records  
   - Expect: records=ok transitions=true isolation=true

### Limitations
- Verified on the elixir-1.18 template at s-1vcpu-1gb with the example fixture; other sizes, templates and Phoenix major versions are not verified.
- The recruiting tracker itself (your record schema, states and access rules) is application code and was not separately tested; the pattern checks are what was verified.
- Region, compliance attestations, and request-duration limits are unknown and not claimed.

### Cost Estimate
- Currency: USD  
- Monthly Amount: $10.00  
- Authoritative: true  
- Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty

### Components
1. **App server**  
   - Size: s-1vcpu-1gb  
   - Quantity: 1.0  
   - Monthly Amount: $5.00

2. **Managed PostgreSQL database**  
   - Size: s-1vcpu-1gb  
   - Quantity: 1.0  
   - Monthly Amount: $5.00

### Evidence Summary
1. **Canary run**  
   - Summary: 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; checks passed for relational-records and configuration-secrets.
   - Observed At: 2026-09-20T23:45:31Z

### Last Verified At
2026-09-20T23:45:31Z