# How to deploy a Rails app

Deploy a Rails app to Ample with your coding agent, the CLI or MCP, using build and start commands verified on November 6, 2026.

## the short version

To deploy a Rails app on Ample, run `ample deploy . --name <app-name> --public` in the project directory, or ask your coding agent to deploy it to Ample. Ample builds it on the `ruby-3.4` template, starts it with `bundle exec rails server -b 0.0.0.0 -p $PORT` and returns a public HTTPS URL.

## Deploy Rails

1. **Ask your coding agent.** Install the Ample CLI and create an account, then ask your agent: "Deploy this Rails app to Ample".
    
    ```
    $ curl -fsSL https://get.ample.computer/install.sh | sh
    $ ample auth signup
    ```

2. **Or deploy from the CLI.** It waits until the app is live or failed and prints the URL.
    
    ```
    $ ample deploy . --name <app-name> --public
    ```

3. **Or use MCP.** Call `ample_deploy` on `https://api.ample.computer/mcp` (or `ample mcp` over stdio).

4. **Verify.** On failure read `ample logs <deployment_id> --kind build`, fix the cause and deploy again.

## Tested configuration

|     |     |
| --- | --- |
| Template | `ruby-3.4` |
| 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` |
| Tested size | `s-1vcpu-1gb` |

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`.

Last verification (2026-11-06): 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.

## You need

- 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

## Know the limits

- Verified on the `ruby-3.4` template at `s-1vcpu-1gb`.

## Move a Rails app to Ample

- [How to move a Rails app from AWS EC2 to Ample](/content/migrate/aws-ec2-app/rails/index.html)
- [How to move a Rails app from DigitalOcean Droplet to Ample](/content/migrate/digitalocean-droplet-app/rails/index.html)
- [How to move a Rails app from Fly.io to Ample](/content/migrate/fly-io-app/rails/index.html)
- [How to move a Rails app from Heroku to Ample](/content/migrate/heroku-app/rails/index.html)
- [How to move a Rails app from Netlify to Ample](/content/migrate/netlify-web-app/rails/index.html)
- [How to move a Rails app from Railway to Ample](/content/migrate/railway-app/rails/index.html)
- [How to move a Rails app from Render web service to Ample](/content/migrate/render-web-service/rails/index.html)
- [How to move a Rails app from Vercel to Ample](/content/migrate/vercel-app/rails/index.html)

## Frequently asked questions

### Do I need a Dockerfile to deploy Rails?

No Dockerfile needed: Ample Computer detects Rails from the repository and builds it from source on the `ruby-3.4` template.

### How do I add a database to a Rails app?

Leave `DATABASE_URL` unset and deploy: when the code needs Postgres, MySQL, Redis or MongoDB, Ample creates a managed database and passes its connection string to the app. See [Connect Postgres for Rails](/content/guides/rails/database-connection/index.html).

### What if the deploy fails?

`ample deploy` waits until the app is live or failed. A failure returns who must act, a diagnosis and a suggested fix; read the logs with `ample logs <deployment_id> --kind build`. See [Diagnose deployment failures for Rails](/content/guides/rails/deployment-diagnostics/index.html).
