# Host member portal with Rails: tenant-scoped workspaces

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

## Summary

- **Family**: Workload recipe
- **Framework**: Rails
- **Workload**: Member portal
- **Release Status**: published
- **Support Status**: verified
- **Execution Status**: ready

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

## Resource Requirements
- **Compute**
- **Postgres**

## Infrastructure Requirements

1. **Compute**  
   Verified: 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**  
   Verified: 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
1. 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).
2. A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env).
3. An Ample account token with servers:write, databases:read.

## Workflow Steps
1. **Build and start**  
   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**  
   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`

## 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 Reference**: tests/deploy-canaries/rails-patterns

## Success Checks
1. **Check**: app responds on its public URL  
   **Kind**: http_get  
   **Path**: /  
   **Expect**: ample canary rails patterns
2. **Check**: 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 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
- **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
1. **Kind**: canary_run  
   **Summary**: Rails pattern fixture deployed on Ample; checks passed for multi-tenant-relational-data and configuration-secrets.  
   **Observed At**: 2026-09-20T21:55:28Z  
   **Implementation Revision**: 4f7cb9813c1f-dirty
2. **Kind**: canary_run  
   **Summary**: The same Rails app deployed with a --release-command migration.  
   **Observed At**: 2026-09-20T21:55:28Z  
   **Implementation Revision**: 4f7cb9813c1f-dirty

## Next Actions
1. **Action**: Browse the catalog index  
   **Method**: GET  
   **Relative Path**: /v1/catalog
2. **Action**: Search published recipes by intent, stack and constraints  
   **Method**: POST  
   **Relative Path**: /v1/catalog/search  
3. **Action**: Prepare a side-effect-free deployment plan for an authorized project  
   **Method**: POST  
   **Relative Path**: /v1/catalog/plan