# Host crm with Rails: downloadable reports

Deploy a crm built with Rails on Ample using the generated downloads 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: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). Not separately tested: your export formats, retention policy and entitlement model; treat the crm-specific behavior as your application code.

## Representative Queries
* Host crm with Rails: downloadable reports
* Where can I host CRM built with Rails?
* I need an export query, generated artifact retention and authorized download flow.

## Resource Requirements
* primitive:compute
* primitive:postgres
* primitive: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**  
   The fixture's module implements generated downloads: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). 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/generated-downloads) from the example; then run your own checks. On failure read `ample logs  --kind build` then `--kind runtime`.
   ```
   ample logs  --kind build
   ```

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

## Success Checks
* **App responds on its public URL**  
   kind: http_get  
   path: /  
   expect: ample canary rails patterns
* **Generated-downloads self-test**  
   kind: http_get  
   path: /p/generated-downloads  
   expect: export=ok rows=3 (with ?token=...; 401 without)

## 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 crm itself (your export formats, retention policy and entitlement model) 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.