## Host recruiting tracker with Rails: CSV imports

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

### Framework
- **Rails**

### Workload
- **Recruiting tracker**

### Release Status
- **Published**

### Support Status
- **Verified**

### Execution Status
- **Ready**

### 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

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

### 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. The server must bind 0.0.0.0 on PORT.`

2. **Implement the pattern on PostgreSQL**  
   `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.  
   `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.  
   `ample logs --kind build` then `--kind runtime`.

### Cost Estimate
- **Currency:** USD
- **Monthly Amount:** 10.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.

### 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 recruiting tracker itself (your import format, mapping and conflict rules) is application code and was not separately tested; the pattern checks are what was verified.
  
### Success Checks
- The app responds on its public URL
- Bulk-import-staging self-test

### Evidence Summary
- **Rails pattern fixture deployed on Ample**: Rails pattern fixture deployed on Ample (bundle install into vendor/bundle from Gemfile.lock) checks passed for bulk-import-staging and configuration-secrets.

### Examples
- **Rails pattern fixture**: Multi-pattern Rails app whose bulk import staging module was checked live; the module is under tests/deploy-canaries/_pattern-modules.