Host storefront with Rails: inventory imports

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

Representative Queries

• Host storefront with Rails: inventory imports
• Where can I host Storefront 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

1. Compute

   • Status: verified
   • Summary: 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

   • Status: verified
   • Summary: 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

   • Status: verified
   • Summary: 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 (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

1. App responds on its public URL

   • Kind: http_get
   • Path: /
   • Expect: ample canary rails patterns

2. Bulk-import-staging self-test

   • Kind: http_get
   • Path: /p/bulk-import-staging
   • Expect: 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 storefront 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

• Currency: USD
• Monthly Amount: 10.0
• Basis: size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty
• 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
• Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

Evidence Summary

• Canary Run: Rails pattern fixture deployed on Ample; checks passed for bulk-import-staging and configuration-secrets.
• Last Verified At: 2026-09-20T21:55:28Z

Formats

• HTML
• Markdown
• JSON

Next Actions

1. Browse the catalog index

   • Action ID: browse-catalog
   • Method: GET
   • Relative Path: /v1/catalog

2. Search published recipes by intent, stack and constraints

   • Action ID: search-recipes
   • Method: POST
   • Relative Path: /v1/catalog/search
   • Parameters: body: { limit: 5, query: "Host storefront with Rails: inventory imports" }

3. Prepare a side-effect-free deployment plan for an authorized project

   • Action ID: plan:page:recipes:storefront:rails:inventory-imports
   • Method: POST
   • Relative Path: /v1/catalog/plan
   • Parameters: { inputs: {}, projectId: "", recipeId: "page:recipes:storefront:rails:inventory-imports", recipeRevision: "r1" }