## Host partner portal with Rails: private documents

Deploy a partner portal built with Rails on Ample using the private document library 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, a private S3-compatible bucket holds objects with credentials delivered as encrypted environment variables. Verified on Rails: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok). Not separately tested: your identity integration and role assignments; treat the partner portal-specific behavior as your application code.

### Summary
- **Framework:** Rails  
- **Workload:** Partner portal  
- **Release Status:** Published  
- **Support Status:** Verified  
- **Execution Status:** Ready

### Resource Requirements
- **Compute**  
- **Postgres**  
- **S3-compatible object storage**

### 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.  
- **S3-compatible object storage**: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

### Prerequisites
1. A Rails project that builds and starts with the documented commands.  
2. A PostgreSQL driver reading DATABASE_URL at runtime.  
3. A bucket from `ample bucket create` with its credentials passed as encrypted S3_* environment variables.  
4. An Ample account token with servers:write, databases:read, buckets: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.`
2. **Implement the Pattern on PostgreSQL**: The fixture's module implements private document library: a role-to-document access model with negative tests and a private-bucket round-trip for the allowed role.
3. **Wire Object Storage**: Create the bucket(s) and pass endpoint, region, bucket and keys as --env values.
4. **Deploy**: Run the synchronous deploy once and read the result.  
5. **Verify**: Fetch the live URL and the pattern self-test route(s) and then run your own checks.

### Success Checks
- **App responds on its public URL**  
- **Private-document-library self-test**

### 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 identity integration and role assignments) is application code and was not separately tested.

### Cost Estimate
- **Monthly Amount**: $10.0 (USD)  
  - **App Server**: s-1vcpu-1gb  
  - **Managed PostgreSQL Database**: s-1vcpu-1gb
  - 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.