page:guides:rails:build and start

Configure build and start for Rails

Summary

Build and start for a Rails app on Ample. Verified on Rails: the app built and started with the documented commands and answered on its public HTTPS URL. 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.

Prerequisites

A Rails project (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)
An Ample account token with servers:write

Workflow Steps

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.
Deploy
Run the synchronous deploy once and read the result.
Command: ample deploy . --name --public
Verify
Fetch the live URL on the example; on failure read the build and runtime logs.
Command: ample logs --kind build

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

Success Checks

App responds on its public URL
Kind: http_get
Path: /
Expect: ample canary rails patterns

Limitations

Verified on the ruby-3.4 template at s-1vcpu-1gb; other sizes and Rails major versions are not verified.
Region, compliance attestations, and request-duration limits are unknown and not claimed.

Cost Estimate

Currency: USD
Monthly Amount: 5.0
Note: Always-on monthly price of the tested sizes; apps auto-pause when idle. Buckets are allocation-priced per quota and not included.

Evidence Summary

Summary: Rails pattern fixture deployed on Ample; for this guide: the app built and started with the documented commands and answered on its public HTTPS URL.
Observed At: 2026-09-20T21:55:28Z
Expires At: 2027-03-19T21:55:28Z