Frameworks/Deploy Rails on your own server
Rails

Deploy Rails on your own server

Push a Rails app and Railpack installs your gems, precompiles the assets and starts it, on a server you own.

From repo to live in three steps

  1. 01Connect the repository that holds your Rails app.
  2. 02Railpack recognises the Rails project and builds it into an image.
  3. 03Push to the branch: every push builds and rolls out a new version.

What Deplo sets up

  • Recognised from config/application.rb.
  • Gems installed for production, with the Bundler version from Gemfile.lock.
  • Assets precompiled when the app uses Sprockets or Propshaft; API-only apps skip it.
  • Node.js installed when the app has a package.json or uses execjs.

Deplo builds with Railpack by default, so a Rails project needs no Dockerfile to get started.

Rails on Deplo

Short answers to what comes up before moving a Rails app onto your own server.

Yes. Managed databases live in the same environment and reach the app over the internal network.

In the app's settings, per environment. They are available during the build too, and secret values are write only: nothing reads them back.

No. The new container has to pass its health check before the old one is retired.

Ten minutes from now,
it's live.

Answer three questions and pick a host, or install Deplo on a server you already have. It's free, and leaving is as easy as arriving. What you do with the money you save is your business.