### Host admin dashboard with Rails: public profile assets

Deploy an admin dashboard built with Rails on Ample using the public image delivery 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, and a published bucket serves public assets from the CDN host. Verified on Rails: public objects in a published bucket served from the CDN URL, kept separate from private objects in an unpublished bucket that require authorization (private=ok only for the allowed role). Not separately tested: your image processing and profile-media rules; treat the admin dashboard-specific behavior as your application code.

#### Representative Queries
- Host admin dashboard with Rails: public profile assets
- Where can I host Admin dashboard built with Rails?
- I need separate public profile media from private data, with CDN cache rules.

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

#### 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.
3. **S3-compatible object storage**:  
   - Status: verified  
   - Summary: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.
4. **CDN**:  
   - Status: verified  
   - Summary: The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.

#### 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 and a second, published bucket for public assets (CDN_*)
- An Ample account token with servers:write, databases:read, buckets:read

#### Workflow Steps
1. **Build and start**:  
   - Run: 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 public image delivery: public objects in a published bucket served from the CDN URL, kept separate from private objects in an unpublished bucket that require authorization (private=ok only for the allowed role). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.
3. **Wire object storage**:  
   - 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. Publish only the bucket that serves public assets and reference its CDN URL.
4. **Deploy**:  
   - Run the synchronous deploy 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=... --env CDN_PUBLIC_URL=...`
5. **Verify**:  
   - Fetch the live URL and the pattern self-test route(s) (/p/public-media-library, /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`

#### Success Checks
- App responds on its public URL (HTTP GET "/"): Expected response - ample canary rails patterns
- Public-media-library self-test (HTTP GET "/p/public-media-library"): Expected response - a CDN URL whose content is served publicly
- Private-document-library self-test (HTTP GET "/p/private-document-library"): Expected response - private=ok (with ?role=owner; 401 without, 403 for viewer)

#### 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 admin dashboard itself (your image processing and profile-media rules) is application code and was not separately tested; the pattern checks are what was verified.

#### Cost Estimate
- **Currency**: USD  
- **Monthly Amount**: 10.0  
- **Components**:  
  - App server: **size** s-1vcpu-1gb, **quantity** 1.0, **monthlyAmount** 5.0  
  - Managed PostgreSQL database: **size** s-1vcpu-1gb, **quantity** 1.0, **monthlyAmount** 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; checks passed for public-media-library, private-document-library and configuration-secrets.  
   - Observed At: 2026-09-20T21:55:28Z
   - Expires At: 2027-03-19T21:55:28Z
2. **Unknowns**:  
   - Region availability is unknown until a verified region fact is recorded.
   - Compliance attestations are unknown; none are claimed.

### Formats
- **HTML**: [Link](/content/recipes/admin-dashboard/rails/public-profiles/index.html)
- **Markdown**: [Link](/content/recipes/admin-dashboard/rails/public-profiles.md)
- **JSON**: [Link](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Aadmin-dashboard%3Arails%3Apublic-profiles)

### Next Actions
1. **Browse the catalog index**
2. **Search published recipes by intent, stack and constraints** 
3. **Prepare a side-effect-free deployment plan for an authorized project** 
4. **Read the existing agent authentication setup** 
5. **Browse Admin dashboard** 
6. **Browse Rails** 
7. **Browse Public image delivery** 
8. **Browse Deploy web app**