### Host project tracker with Phoenix: relational workspace data

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

#### Summary  
- **Family:** Workload recipe  
- **Framework:** Phoenix  
- **Workload:** Project tracker  
- **Release Status:** published  
- **Support Status:** verified  
- **Execution Status:** ready  
- **Docs Only:** false

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

#### Resource Requirements  
- **Compute**  
- **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.

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.

#### 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  --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  --kind build` then `--kind runtime`.
   - **Command:** ample logs  --kind build

#### Examples  
- **Title:** Phoenix pattern fixture  
  - **Description:** Multi-pattern Phoenix app whose relational records module was checked live; the module is under tests/deploy-canaries/_pattern-modules.  
  - **Source Reference:** tests/deploy-canaries/phoenix-patterns

#### 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 project 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.  
- Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.  
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.