## Host documentation site with Rails: bulk content imports

Deploy a documentation site built with Rails on Ample using the bulk import staging 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 CSV staged as an object, row-level validation with per-row errors recorded, and a restart-safe import keyed by import id (imported=2 rejected=1 restart=ok). Not separately tested: your import format, mapping and conflict rules; treat the documentation site-specific behavior as your application code.

### Representative Queries
- Host documentation site with Rails: bulk content imports
- Where can I host Documentation site built with Rails?
- I need a staged import format, validation procedure and import recovery workflow.

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

### Infrastructure Requirements
1. **Compute**  
   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
2. **Postgres**  
   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
3. **S3-compatible object storage**  
   Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.  
   Status: verified

### 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**  
   Run `bundle install` into vendor/bundle from Gemfile.lock, then start Puma with `rails server`.
2. **Implement the pattern on PostgreSQL**  
   Make sure the fixture's module implements bulk import staging. Keep migrations idempotent.
3. **Wire object storage**  
   Create the bucket(s) and pass required data as environment variables.
4. **Deploy**  
   Run the synchronous deploy and read the result.
5. **Verify**  
   Fetch the live URL and run your own checks.

### Limitations
- Verified on the ruby-3.4 template; other sizes are not verified.
- The behavior specific to the documentation site is application code and was not separately tested.

### Cost Estimate
**Monthly Amount:** $10.00  
- App server (s-1vcpu-1gb): $5.00  
- Managed PostgreSQL database (s-1vcpu-1gb): $5.00  
*Note: Buckets are allocation-priced per quota and not included.*

### Success Checks
- App responds on its public URL
- Bulk-import-staging self-test

### 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 existing agent authentication setup