Updating ruby on rails
If you don't already have a Github account, make sure to register. You'll probably want something more robust like My SQL or Postgre SQL.There is a lot of documentation on both, so you can just pick one that seems like you'll be more comfortable with.If you're coming from PHP, you may already be familiar with My SQL.If you're new to databases, I'd suggest skipping to setting up Postgre SQL.There are plenty of people who have documented solutions for them. Homebrew allows us to install and compile software packages easily from source. When it asks you to install XCode Command Line Tools, say yes.Open Terminal and run the following command: We'll be using Git for our version control system so we're going to set it up to match our Github account. Chances are you won't want to use it because it's stored as a simple file on disk.
We can then install a specific version, such as sub-command, rbenv maintains shims in that directory to match every Ruby command across every installed version of Ruby on your server.
We have covered the basics of how to install rbenv and Ruby on Rails here so that you can use multiple Ruby environments.
For your next steps, you can learn more about making those environments more robust.
You start coding, a process that can take some time (weeks or months, even). The first thing you have to keep in mind is that you do have a better chance by doing small upgrades. there are lots of changes between these releases, with deprecations and even feature removal, but doing it in small doses will make your life way easier.
It doesn’t take long, until you can’t upgrade your project to a new Rails version. Are you running Rails 3.2.21 and want to upgrade to Rails 4.2.1? Your chances of doing it successfully will increase if you first upgrade to 4.0.13, then 4.1.9, and, finally, Rails 4.2.1. Ruby on Rails follows a versioning scheme based on Sem Ver.