page:recipes:inventory manager:rails:report exports

Host Inventory Manager with Rails: Downloadable Reports

Deploy an inventory manager 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 inventory manager-specific behavior as your application code.

Representative Queries

• Host inventory manager with Rails: downloadable reports
• Where can I host Inventory Manager 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

Infrastructure Requirements

• Compute: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
• 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.
• 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

1. 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).
2. A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env).
3. A bucket from ample bucket create with its credentials passed as encrypted S3_* environment variables.
4. An Ample account token with servers:write, databases:read, buckets:read.

Workflow Steps

1. Build and Start: bundle install into vendor/bundle from Gemfile.lock, then Puma via rails server reading PORT.
2. Implement the Pattern on PostgreSQL: The fixture's module implements generated downloads: copy the approach into your schema; keep migrations idempotent.
3. Wire Object Storage: Create the bucket(s), then pass endpoint, region, bucket and keys as --env values.
4. Deploy: Run the synchronous deploy once and read the result.
5. Verify: Fetch the live URL and the pattern self-test route(s).

Success Checks

• App responds on its public URL
• Generated-downloads self-test

Limitations

• Verified on the ruby-3.4 template at s-1vcpu-1gb; other sizes, templates and Rails major versions are not verified.
• The inventory manager itself (your export formats, retention policy and entitlement model) is application code and was not separately tested.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Components:
  • App server: size s-1vcpu-1gb, quantity 1, monthlyAmount 5.0
  • Managed PostgreSQL database: size s-1vcpu-1gb, quantity 1, monthlyAmount 5.0
  • Note: Always-on monthly price.