## Host member portal with Phoenix: tenant-scoped workspaces

### Summary
Deploy a member portal built with Phoenix on Ample using the multi-tenant relational data 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 tenant column on every row and query, with a cross-tenant read returning nothing (tenant_isolation=ok). Not separately tested: your tenant model, membership and per-tenant authorization; treat the member portal-specific behavior as your application code.

### Representative Queries
- Host member portal with Phoenix: tenant-scoped workspaces
- Where can I host Member portal built with Phoenix?
- I need an explicit tenant model and application-enforced tenant isolation tests.

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

### 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 multi-tenant relational data: a tenant column on every row and query, with a cross-tenant read returning nothing (tenant_isolation=ok). 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/multi-tenant-relational-data) 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 member portal itself (your tenant model, membership and per-tenant authorization) 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
- **Components**:
  - App server: s-1vcpu-1gb - Quantity: 1.0 - Monthly Amount: 5.0
  - Managed PostgreSQL database: s-1vcpu-1gb - Quantity: 1.0 - Monthly Amount: 5.0
- **Note**: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

### Next Actions
- **Browse the catalog index**: GET `/v1/catalog`
- **Search published recipes by intent, stack and constraints**: POST `/v1/catalog/search` (Body: `{"limit":5,"query":"Host member portal with Phoenix: tenant-scoped workspaces"}`)
- **Prepare a side-effect-free deployment plan for an authorized project**: POST `/v1/catalog/plan` (Body: `{"inputs":{},"projectId":"","recipeId":"page:recipes:member-portal:phoenix:tenant-workspaces","recipeRevision":"r1"}`)
- **Read the existing agent authentication setup**: GET `/mcp/setup`
- **Browse Member portal**: GET `/v1/catalog/nodes/workload%3Amember-portal`
- **Browse Phoenix**: GET `/v1/catalog/nodes/stack%3Aframework-phoenix`
- **Browse Multi-tenant relational data**: GET `/v1/catalog/nodes/pattern%3Amulti-tenant-relational-data`
- **Browse Deploy web app**: GET `/v1/catalog/nodes/intent%3Adeploy-web-app`

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