page:recipes:subscription content:rails:inventory imports

Host subscription content with Rails: inventory imports

Summary

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

Representative Queries

• Host subscription content with Rails: inventory imports
• Where can I host Subscription content built with Rails?
• I need an inventory import contract, staging objects and row-level error handling.

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.

Framework

Rails

Workload

Subscription content

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

Tested Configuration

• Template: ruby-3.4
• Runtime: ruby
• Size: s-1vcpu-1gb
• Install: bundle config set --local path vendor/bundle && bundle config set --local without 'development test' && bundle install
• Start: bundle exec rails server -b 0.0.0.0 -p $PORT

Workflow Steps

1. Build and start: bundle install into vendor/bundle from Gemfile.lock, then start the server.
2. Implement the pattern on PostgreSQL: The fixture's module implements bulk import staging.
3. Wire object storage: Create the buckets and pass values as --env values.
4. Deploy: Run the synchronous deploy once and read the result.
5. Verify: Fetch the live URL and run your own checks.

Examples

• Rails pattern fixture: Multi-pattern Rails app whose bulk import staging module was checked live.

Success Checks

• App responds on its public URL.
• Bulk-import-staging self-test.

Limitations

• Verified on the ruby-3.4 template. Other sizes and versions are not verified.
• The subscription content itself is application code and was not separately tested.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Components:
  • App server: s-1vcpu-1gb, quantity: 1.0, monthly amount: 5.0
  • Managed PostgreSQL database: s-1vcpu-1gb, quantity: 1.0, monthly amount: 5.0

Evidence Summary

• Canary Run: Rails pattern fixture deployed on Ample; checks passed.

Last Verified At

• 2026-09-20T21:55:28Z

Unknowns

• Region availability is unknown until verified.

Next Actions

• Browse the catalog index.
• Search published recipes by intent, stack and constraints.
• Prepare a side-effect-free deployment plan for an authorized project.