## Host vendor portal with Rails: tenant-scoped workspaces

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

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

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

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

### Framework
Rails

### Workload
Vendor portal

### Release Status
published

### Support Status
verified

### Execution Status
ready

### 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 Command**: bundle config set --local path vendor/bundle && bundle config set --local without 'development test' && bundle install
- **Start Command**: bundle exec rails server -b 0.0.0.0 -p $PORT

### 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.
   ```bash
   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`.
   ```bash
   ample logs  --kind build
   ```

### 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 vendor 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
- **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.
- **Components**:
  - app server
    - Size: s-1vcpu-1gb
    - Quantity: 1.0
    - Monthly Amount: 5.0
  - managed PostgreSQL database
    - Size: s-1vcpu-1gb
    - Quantity: 1.0
    - Monthly Amount: 5.0

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