Back

Ruby on Rails VPS Hosting, Pre-Installed

Ruby on Rails hosting on this server gives you a running project with Ruby, Rails 8, Puma, SQLite and HTTPS already in place. The sample project is generated and goes live by itself after payment, and its address appears in your panel. Connect over SSH and work in /home/app/uygulama, or bring your own project into that folder.

How much power do you need?

Total$2.58/mo

Prices include VAT.

Scale RAM and CPU up or down whenever you like. Disk can only grow, so start small.

What's installed on your Ruby on Rails server?

  • Ruby 3.2 from the Ubuntu 24.04 repository
  • Rails 8 (8.1 or later) and a sample project in /home/app/uygulama
  • Puma on 127.0.0.1:3000, running as a systemd service called uygulama
  • SQLite, with the production database at storage/production.sqlite3
  • HTTPS through Caddy with force_ssl on in Rails, so a domain is optional
  • Settings in /etc/seturack-rails.env: RAILS_ENV=production and a generated SECRET_KEY_BASE
  • build-essential and development libraries for compiling gems, plus a 2 GB swap file
  • Firewall with only ports 22, 80 and 443 open

What size do you need for Ruby on Rails?

The Rails documentation gives no RAM figure. Memory depends on Puma's process and thread counts, your gems and assets:precompile. As a rule of thumb, 1 GB suits trials and small projects, and 2 to 4 GB is a good start for a project with real traffic. The smallest size is 1 GB of RAM, 1 CPU and a 15 GB disk, and the install adds 2 GB of swap for builds. If it isn't enough, scale up from your panel and set the number of Puma processes with WEB_CONCURRENCY.

UseSizePriceChoose
Starter 1 GB RAM · 1 vCore · 25 GB NVMe $2.58/mo
Medium 2 GB RAM · 1 vCore · 40 GB NVMe $4.01/mo
Powerful 4 GB RAM · 2 vCore · 60 GB NVMe $6.89/mo

Who is it for?

  • Developers who want to run their Rails project on their own server
  • People learning Rails or building a prototype or small product on one server
  • Projects that start on SQLite and may move to PostgreSQL later

What happens after you order?

  1. Set the size and complete your payment.
  2. Your server starts and Ruby and Rails install themselves. This took about 5 minutes in our real-server tests.
  3. Open the Site address from the Overview tab. The sample page shows the Rails version.
  4. Connect over SSH, type su - app, move to ~/uygulama and load the settings from /etc/seturack-rails.env into your shell.
  5. After changing your code, run bundle install, bin/rails db:migrate and bin/rails assets:precompile.
  6. Restart Puma with systemctl restart uygulama as root.

With every server

  • Daily backups included in the price
  • Unlimited traffic
  • Full root access
  • Scale RAM and CPU up or down later, and grow the disk
  • Location: Istanbul · IST-1.

Good to know

  • The sample project is deliberately bare: it has no Hotwire, Action Cable, Solid Queue or Kamal setup. When you bring your own project, bundle install adds whatever your Gemfile lists.
  • HTTPS enforcement lives in config/initializers/seturack.rb. Keep that file when you bring your own project, or set assume_ssl and force_ssl yourself.
  • If your project uses Rails credentials, add RAILS_MASTER_KEY to /etc/seturack-rails.env.
  • Ruby 3.2 is what's installed. If your project needs a newer Ruby, install it yourself and update the PATH line in the service file.
  • Keeping your gems and Rails up to date is your responsibility. Ubuntu security updates install themselves.

Ruby on Rails questions and answers

How do I bring my own Rails project to the server?

Connect over SSH and type su - app. Rename the sample project, clone your code into ~/uygulama with git clone and copy config/initializers/seturack.rb across. Run bundle install, bin/rails db:prepare and bin/rails assets:precompile, then systemctl restart uygulama as root.

How do I run Rails commands on the server?

Type su - app and cd ~/uygulama. Load the settings with set -a; . /etc/seturack-rails.env; set +a. Add the gem path with export PATH=$GEM_HOME/bin:$PATH. After that, bundle, bin/rails console and bin/rails db:migrate use your production settings.

How much RAM does Ruby on Rails need?

Rails has no official RAM figure. As a rule of thumb, 1 GB suits trials and small projects, and 2 to 4 GB is a good start for real traffic. Adding Puma processes uses more memory than adding threads.

Can I use PostgreSQL instead of SQLite?

Yes. Run apt install postgresql libpq-dev as root, add pg to your Gemfile, change the production section of config/database.yml and run bin/rails db:prepare. You can also put the database on a separate server.

Which Ruby and Rails versions are installed?

You get Ruby 3.2 from Ubuntu 24.04 and the latest Rails 8 release at install time (8.1 or later). The Rails guides say Rails 8.0 and 8.1 require Ruby 3.2.0 or newer.

Is there a Rails health check address?

Yes. Rails's own /up path is open and returns 200 while the app is running. It's excluded from the HTTPS redirect, so you can point your monitoring tool straight at it.

Read more and see similar apps