## Host reporting dashboard with Rails: structured data imports

Deploy a reporting dashboard 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 reporting dashboard-specific behavior as your application code.

### Representative Queries
- Host reporting dashboard with Rails: structured data imports
- Where can I host Reporting dashboard built with Rails?
- I need a workload-specific import mapping, conflict rules and restart behavior.

### Infrastructure Requirements
1. **Compute**  
   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**  
   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**  
   Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not 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 (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 bulk import staging: 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). 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.

4. **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. 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**  
   Fetch the live URL and the pattern self-test route(s) (/p/bulk-import-staging) 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. Expected response: `ample canary rails patterns`.
- Bulk-import-staging self-test. Expected response: `imported=2 rejected=1 restart=ok`.

### 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 reporting dashboard itself (your import format, mapping and conflict rules) is application code and was not separately tested; the pattern checks are what was verified.

### Cost Estimate
- **Monthly Amount:** $10.00 (USD)
  - **app server:** s-1vcpu-1gb (1.0) - $5.00
  - **managed PostgreSQL database:** s-1vcpu-1gb (1.0) - $5.00
  - 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**  
   Rails pattern fixture deployed on Ample; checks passed for bulk-import-staging and configuration-secrets.
   - Observed at: 2026-09-20T21:55:28Z
   - Expires at: 2027-03-19T21:55:28Z

2. **Canary run**  
   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
   - Expires at: 2027-03-19T21:55:28Z

### Formats
- [HTML format](/content/recipes/reporting-dashboard/rails/data-imports/index.html)
- [Markdown format](/content/recipes/reporting-dashboard/rails/data-imports.md)
- [JSON format](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Areporting-dashboard%3Arails%3Adata-imports)