# Host member portal with Rails: private documents

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

## Representative Queries
- Host member portal with Rails: private documents
- Where can I host Member portal built with Rails?
- I need a role-to-document access model and negative authorization tests.

## Resource Requirements
- primitive:compute
- primitive:postgres
- primitive:s3-compatible-object-storage

## Infrastructure Requirements
1. **Compute**  
   - **Summary:** Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.  
   - **Status:** verified  
   - **Canonical Path:** /discover/primitive/compute

2. **Postgres**  
   - **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.  
   - **Status:** verified  
   - **Canonical Path:** /discover/primitive/postgres

3. **S3-compatible object storage**  
   - **Summary:** Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.  
   - **Status:** verified  
   - **Canonical Path:** /discover/primitive/s3-compatible-object-storage

## 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)
- A bucket from `ample bucket create` with its credentials passed as encrypted S3_* environment variables
- An Ample account token with servers:write, databases:read, buckets:read

## 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 private document library: 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). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.

3. **Wire object storage**  
   - **Body:** Create the bucket(s), then pass endpoint, region, bucket and keys as --env values. Use path-style addressing. Keep private data in an unpublished bucket.

4. **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 --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...

5. **Verify**  
   - **Body:** Fetch the live URL and the pattern self-test route(s) (/p/private-document-library) 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 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 identity integration and role assignments) 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.
- PutObject and GetObject with path-style addressing are verified; multipart upload, listing, presigned URLs and lifecycle rules are not verified.

## Cost Estimate
- **Currency:** USD  
- **Monthly Amount:** 10.0  
- **Authoritative:** true  
- **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. **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 private-document-library and configuration-secrets. Pattern proof: 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).  
   - **Observed At:** 2026-09-20T21:55:28Z  
   - **Implementation Revision:** 4f7cb9813c1f-dirty (CLI 4f7cb98)  
   - **Expires At:** 2027-03-19T21:55:28Z

2. **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  
   - **Implementation Revision:** 4f7cb9813c1f-dirty (CLI 4f7cb98)  
   - **Expires At:** 2027-03-19T21:55:28Z

## Formats
- [HTML](/content/recipes/member-portal/rails/private-documents/index.html)  
- [Markdown](/content/recipes/member-portal/rails/private-documents.md)  
- [JSON](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Amember-portal%3Arails%3Aprivate-documents)

## Next Actions
1. **Browse the catalog index**  
   - **Action ID:** browse-catalog  
   - **Method:** GET  
   - **Relative Path:** /v1/catalog  
   - **Requires Authentication:** false  
   - **Requires Approval:** false

2. **Search published recipes by intent, stack and constraints**  
   - **Action ID:** search-recipes  
   - **Method:** POST  
   - **Relative Path:** /v1/catalog/search  
   - **Parameters:** {"body":{"limit":5,"query":"Host member portal with Rails: private documents"}}  
   - **Requires Authentication:** false  
   - **Requires Approval:** false

3. **Prepare a side-effect-free deployment plan for an authorized project**  
   - **Action ID:** plan:page:recipes:member-portal:rails:private-documents  
   - **Method:** POST  
   - **Relative Path:** /v1/catalog/plan  
   - **Requires Authentication:** true  
   - **Requires Approval:** false

4. **Read the existing agent authentication setup**  
   - **Action ID:** auth-setup  
   - **Method:** GET  
   - **Relative Path:** /mcp/setup  
   - **Requires Authentication:** false  
   - **Requires Approval:** false

5. **Browse Member portal**  
   - **Action ID:** browse:workload:member-portal  
   - **Method:** GET  
   - **Relative Path:** /v1/catalog/nodes/workload%3Amember-portal  
   - **Requires Authentication:** false  
   - **Requires Approval:** false