# Host approval workflow with Phoenix: relational workspace data

Deploy a approval workflow 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 approval workflow-specific behavior as your application code.

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

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

## Infrastructure Requirements
- **Compute**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
- **Postgres**: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

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

## 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 approval workflow 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.

## Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Basis**: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
- **Components**:
  - **App Server**: size=s-1vcpu-1gb, quantity=1.0, monthlyAmount=5.0
  - **Managed PostgreSQL Database**: size=s-1vcpu-1gb, quantity=1.0, monthlyAmount=5.0
- **Note**: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

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

## Success Checks
- **App responds** on its public URL  
  - Path: /  
  - Expect: ample canary phoenix patterns
- **Relational-records self-test**:  
  - Path: /p/relational-records  
  - Expect: records=ok transitions=true isolation=true

## Evidence Summary
- **Kind**: 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; 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).
- **Observed At**: 2026-09-20T23:45:31Z  
- **Implementation Revision**: 4d1511e574302f3904b75088bd4048a0975218b3-dirty (CLI 0.1.21)  
- **Expires At**: 2027-03-19T23:45:31Z

## Next Actions
- **[Browse the catalog index](/v1/catalog)**  
- **[Search published recipes by intent, stack and constraints](/v1/catalog/search)**  
- **[Prepare a side-effect-free deployment plan for an authorized project](/v1/catalog/plan)**  
- **[Read the existing agent authentication setup](/mcp/setup)**  
- **[Browse Approval workflow](/v1/catalog/nodes/workload%3Aapproval-workflow)**  
- **[Browse Phoenix](/v1/catalog/nodes/stack%3Aframework-phoenix)**  
- **[Browse Relational records](/v1/catalog/nodes/pattern%3Arelational-records)**  
- **[Browse Deploy web app](/v1/catalog/nodes/intent%3Adeploy-web-app)**