💊 How To Install #RubyonRails 💊 on Windows 7/8/10 → Complete Tutorial 2019 (February 2019)

1️⃣ Identify Windows Architecture

The first step is to know your Windows version (x64 or x86):

• Press Windows+ R keys on the keyboard
• Type dxdiag and press OK
• Identify the System Type from the list:

2️⃣ Download ZIP From RubyInstaller (may need to install 7Zip):

3️⃣ Save The Zip To Your Hard Drive

4️⃣ Unzip To PERMANENT Folder:

5️⃣ Add to PATH:

The Windows PATH allows your system to load applications be referencing their name. To call ruby from CMD, you’ll need to add it to the PATH var:

→ Windows 7

• Click on Start
• Right-click on Computer → select Properties
• From the System dialogue, select Advanced System Settings:

• Select “Advanced” tab — “Environment Variables”:

• From here, select the PATH variable from the SYSTEM Variables panel, and select Edit:

When the “path” variable setting loads, paste the path to the /bin directory of Ruby into it (keeping the other paths intact). After this, click “OK” to exit.

→ Windows 10

• Press Windows button (keyboard)
• Type ENV + press Enter ↴

• Select Environment Variables ↴

• The following should appear:

• Next, click New to add the bin directory for the new ruby directory you created (also add the devkit bin directory if you’ve installed that):

• Click OK and exit any CMD instances you have open.

🔨 Build Tools 🔨

Next, you need to install “build tools”.

These are used to compile gems that rely on external libraries
(nokogiri / rmagick / mysql2):

—
*ALL* operating systems require build tools as extra downloads. They are applications, files and libraries which help your system compile gems.

In Ubuntu, you’d install the build-essential package:

In Windows, you need to download the tools separately.

How you do this is determined by which version of RubyInstaller you choose. If you used 2.3.x, you use Devkit; 2.4.x + 2.5.x use MSYS2:

—

Devkit (≤ 2.3.x) (Good tutorial)

For older versions (up to 2.3.x) of RubyInstaller, you need “DevKit” ↴

Ruby 2.4.x did away with this, so if you’re planning on using Ruby 2.4.x or Ruby 2.5.x , you’ll be better using MSYS2 directly from their site.

—

ZIP (≤ 2.3.x ONLY → 2.4.x/2.5.x NEEDS to use MSYS2)…

After downloading ONE of the above files, load the self extracting archive and “unzip” to a temporary directory:

Once complete, you need to initialize DevKit and bind it to your Ruby installation:

1. Load up cmd and cd into the RubyGems directory
2. Type the following: ruby init.rb & press Enter
3. Next, load up the config.yml —
4. Add the directory for your Ruby installation:

# devkit/config.yml
# ...
#
# Example:
#
# ---
# - C:/ruby19trunk
# - C:/ruby192dev
#
---
- "C:/Program Files/Ruby200-x64"

• Next, in cmd you should type ruby setup.rb & press Enter
• This should bind DevKit to your Ruby installation, allowing it to call all the libraries.

MSYS2 (STRONGLY Recommended → essential for ≥ 2.4x / 2.5.x)

Ruby 2.4.x / 2.5.x (RubyInstaller2) uses MSYS2 ↴

Setting up MSYS2 is slightly more involved than DevKit, but more effective.

The point is that both install a series of files or applications which allow
you to perform build / compilation operations:

• Download the appropriate version of MSYS2 x86 or x64 :

• Save the installer to your hard drive
• Double-click the installer to get it to load:

• After the installer completes, you need to set up pacman
• Load a new MSYS2 console and type the following:

pacman -Sy pacman

You should see something similar to the following:

Using the above commands, pacman will be installed and ready to use.

Now, you need to install the various build dependencies. This used to be
done from within MSYS2 itself, but now it’s part of the RubyInstaller2 installation process:

• Open up CMD
• Type ridk install
• The following screen should appear:

Press 3 and Enter.

From here, it should work to install the various components of the MSYS2 development toolchain. If this process fails (we had a Windows 8 user where the process hung randomly), you’ll want to switch back to MSYS2 and run one of the following commands (installs the build tools manually):

pacman -S base-devel mingw-w64-i686-toolchain #32-bit
pacman -S base-devel mingw-w64-x86_64-toolchain #64-bit

If this does not work (in Windows 8), you should continually resize the MSYS2 window. This is what it took to get it working on a reader’s system.

—

Installing C-dependent Gems (Nokogiri / SQLite3 etc)

The RubyInstaller2 repo has a good tutorial on how to do this:

⚠️🚨 NOTE ABOUT SQLITE3 🚨⚠️

If you use SQLite3 (as we do in development), you’ll find the latest version of the gem to be incompatible with Windows.

The answer to this is to install the “mingw-w64-x86_64-dlfcn“ package through MSYS2:

This installs the correct package, allowing you to run the SQLite3 1.4.0 gem inside the Windows environment.

📋 RubyGems 📋

Next, you need to install RubyGems.

RubyGems is the repository which stores all the “gems” you can install on Ruby. These gems are the “plugins” for the language, providing functionality.

—

As this is a separate package to Ruby, it has to be installed manually:

To install RubyGems, you need to download the ZIP and
unzip to a temporary folder:

From there, you will need to open cmd.exe and cd into the TEMPORARY folder. You should then type ruby setup.rb and RubyGems willinstall:

If successful, you’ll be able to type gem -v in a new instance of cmd:

🚀 Rails 🚀

With RubyGems installed, you need to install the rails gem:

This should be a very simple procedure → in cmd type…
gem install rails --no-document

• You also need bundler because without it, you cannot use a Gemfile
• You need rails because that’s the framework you’re using.

Installing Rails as a system-wide gem will give you the ability to call it whenever needed, not just as part of a Rails application:

🚦 GIT 🚦

You then need to install GIT.

Git is a source code management system (SCM), basically allowing you to sync your development source with production and staging environments.

It has taken over the role of FTP, allowing you to “push” code to “repositories”. If this sounds alien, you need to read up on it. It’s an essential part of modern web development — especially Rails. Github is a very good place to start:

The installation process should be performed as follows:

Once installed, you should load a new instance of cmd.exe and type the command git — version. If it returns a value, the installation was a success:

💻 IDE (Code Editor) 💻

Finally, you need an IDE (Integrated Development Environment).

Whist you’re free to use Notepad to edit code, the best system is to use a dedicated code editor. The old favorite was Sublime Text, however it was
not updated enough and cost.

We use Atom.io from GitHub (free & open source):

You can download here (free).