Updating to rails 2 2 2

Any bugs with the installer should be reported on Github in the respective repositories ( railsinstaller-windows or railsinstaller-nix ).

Importantly, just because you’re updating one dependency, it doesn’t mean you want to re-resolve all of your dependencies and use the latest version of everything.

Our app was running Rails 2.3.8 at the time, and the production instances were a mess.

Each instance had its own set of gems and its own versions of those gems. One of our engineers picked the latest version of each gem initialized by in production to create our first Gemfile.

The official Rails guide for upgrading from Rails 3.2 to 4.0 is very thorough.

With the recent release of Rails 5.0, apps currently in production running Rails 3.2 should probably be updated to any stable Rails 4 release as soon as possible.

The won't let me upgrade by bundle install and bundle upgrade rails keeps throwing this error: Could not find gem 'rails (= 4.2.2) ruby' in any of the gem sources listed in your Gemfile or installed on this machine. After installing the kit, check out the Rails Guides for information about developing Ruby on Rails applications.Another great resource is the Ruby on Rails Tutorial by Michael Hartl.Resolving all dependencies from scratch can have surprising results, especially if a number of the third-party packages you depend on have released new versions since you last did a full update.There are already quite a few guides in the wild to help with the upgrade of Rails 3.2 to Rails 4.0.

Leave a Reply