# Host partner portal with Rails: tenant-scoped workspaces

### Summary
Deploy a partner portal built with Rails 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 Rails: 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 partner portal-specific behavior as your application code.

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

### 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.
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 Rails project that builds and starts with the documented commands (bundle install into vendor/bundle from Gemfile.lock (development and test groups skipped), then Puma via `rails server` reading PORT on the ruby-3.4 template with RAILS_ENV=production)
- 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

### Tested Configuration
- **Template:** ruby-3.4  
- **Runtime:** ruby  
- **Size:** s-1vcpu-1gb  
- **Install:** `bundle config set --local path vendor/bundle && bundle config set --local without 'development test' && bundle install`  
- **Start:** `bundle exec rails server -b 0.0.0.0 -p $PORT`

### Workflow Steps
1. **Build and start**  
   - Body: bundle install into vendor/bundle from Gemfile.lock (development and test groups skipped), then Puma via `rails server` reading PORT on the ruby-3.4 template with RAILS_ENV=production. The server must bind 0.0.0.0 on PORT.
2. **Implement the pattern on PostgreSQL**  
   - Body: 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**  
   - Body: 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**  
   - Body: 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`

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

### Success Checks
1. **Description:** app responds on its public URL  
   **Kind:** http_get  
   **Path:** /  
   **Expect:** ample canary rails patterns
2. **Description:** multi-tenant-relational-data self-test  
   **Kind:** http_get  
   **Path:** /p/multi-tenant-relational-data  
   **Expect:** tenant_isolation=ok

### Limitations
- Verified on the ruby-3.4 template at s-1vcpu-1gb with the example fixture; other sizes, templates and Rails major versions are not verified.
- The partner 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  
- **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.0  
  2. **Managed PostgreSQL Database**  
     - **Size:** 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.

### Evidence Summary
- **Kind:** canary_run  
  **Summary:** Rails pattern fixture deployed on Ample (bundle install into vendor/bundle from Gemfile.lock (development and test groups skipped), then Puma via `rails server` reading PORT on the ruby-3.4 template with RAILS_ENV=production); checks passed for multi-tenant-relational-data and configuration-secrets. Pattern proof: a tenant column on every row and query, with a cross-tenant read returning nothing (tenant_isolation=ok).  
  **Observed At:** 2026-09-20T21:55:28Z  
  **Expires At:** 2027-03-19T21:55:28Z  
  **Scope:**  
- **Checks:** [/p/multi-tenant-relational-data]  
  - **Pattern:** pattern:multi-tenant-relational-data  
  - **Template:** ruby-3.4

- **Kind:** canary_run  
  **Summary:** The same Rails app deployed with a --release-command migration; the marker it created was readable after activation.  
  **Observed At:** 2026-09-20T21:55:28Z  
  **Expires At:** 2027-03-19T21:55:28Z  
  **Scope:**  
  - **Pattern:** pattern:multi-tenant-relational-data

### Last Verified At
2026-09-20T21:55:28Z

### MCP Binding
- **Registry Ref:** mcp:ample_deploy  
- **Tool Name:** ample_deploy  
- **Schema Hash:** 876465fce906da0c224d62961d3343064108ebe30af80cf1b87094974e948853  
- **Observed At:** 2026-09-21T03:19:59.461917+00:00  
- **Implementation Revision:** 49962bcade4f  
- **Required Scopes:** [servers:write, databases:read]  
- **Binding State:** current

### Unknowns
- region availability is unknown until a verified region fact is recorded
- compliance attestations are unknown; none are claimed

### Formats
- **HTML:** [Link](/content/recipes/partner-portal/rails/tenant-workspaces/index.html)
- **Markdown:** [Link](/content/recipes/partner-portal/rails/tenant-workspaces.md)
- **JSON:** [Link](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Apartner-portal%3Arails%3Atenant-workspaces)

### Next Actions
1. **Action ID:** browse-catalog  
   **Label:** Browse the catalog index  
   **Method:** GET  
   **Relative Path:** /v1/catalog
2. **Action ID:** search-recipes  
   **Label:** Search published recipes by intent, stack and constraints  
   **Method:** POST  
   **Relative Path:** /v1/catalog/search  
   **Parameters:** {"body":{"limit":5,"query":"Host partner portal with Rails: tenant-scoped workspaces"}}
3. **Action ID:** plan:page:recipes:partner-portal:rails:tenant-workspaces  
   **Label:** Prepare a side-effect-free deployment plan for an authorized project  
   **Method:** POST  
   **Relative Path:** /v1/catalog/plan  
   **Parameters:** {"body":{"inputs":{},"projectId":"","recipeId":"page:recipes:partner-portal:rails:tenant-workspaces","recipeRevision":"r1"}}
4. **Action ID:** auth-setup  
   **Label:** Read the existing agent authentication setup  
   **Method:** GET  
   **Relative Path:** /mcp/setup
5. **Action ID:** browse:workload:partner-portal  
   **Label:** Browse Partner portal  
   **Method:** GET  
   **Relative Path:** /v1/catalog/nodes/workload%3Apartner-portal
6. **Action ID:** browse:stack:framework-rails  
   **Label:** Browse Rails  
   **Method:** GET  
   **Relative Path:** /v1/catalog/nodes/stack%3Aframework-rails
7. **Action ID:** browse:pattern:multi-tenant-relational-data  
   **Label:** Browse Multi-tenant relational data  
   **Method:** GET  
   **Relative Path:** /v1/catalog/nodes/pattern%3Amulti-tenant-relational-data
8. **Action ID:** browse:intent:deploy-web-app  
   **Label:** Browse Deploy web app  
   **Method:** GET  
   **Relative Path:** /v1/catalog/nodes/intent%3Adeploy-web-app