Configure build and start for Rails · Ample Computer

Configure build and start for Rails

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.

Verified November 6, 2026

What it runs on

You need

Exact tested configuration

install bundle config set --local path vendor/bundle && bundle config set --local without 'development test' && bundle install

runtime ruby

sizes-1vcpu-1gb

start bundle exec rails server -b 0.0.0.0 -p $PORT

template ruby-3.4

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. Deploy. Run the synchronous deploy once and read the result.

    $ ample deploy . --name <app-name> --public
    
  3. Verify. Fetch the live URL on the example; on failure read the build and runtime logs.

    $ ample logs <deployment_id> --kind build
    

How it was checked

✓ app responds on its public URL· http get/ → “ample canary rails patterns”

Evidence

  1. November 6, 2026 · canary run

Rails pattern fixture deployed on Ample (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); for this guide: the app built and started with the documented commands and answered on its public HTTPS URL.

Tested examples

What it doesn’t cover