Updating rails 2 2

Rated 3.96/5 based on 576 customer reviews

#Install Mysql sudo aptitude install mysql-server #Install ruby package sudo aptitude install ruby ruby1.8-dev ri rdoc irb #Install rubygem sudo ruby rubygems #update rubygem sudo gem update --system #(if there is an error on running gem like "/usr/bin/gem:23: uninitialized constant Gem:: Gem Runner (Name Error)") sudo ln -s /usr/bin/gem1.8 /usr/bin/gem #Install Rails sudo gem install rails #To use sqlite3 sudo aptitude install libsqlite3-dev sudo gem install sqlite3-ruby#Install Apache2 & library sudo aptitude install apache2 #Enable Apache modules sudo a2enmod proxy sudo a2enmod proxy_http sudo a2enmod proxy_balancer sudo a2enmod rewrite #Install Mongrel, Mongrel Cluster sudo gem install mongrel mongrel_cluster #Configure Apacherails trunk cd trunk rm -rf tmp/* log/* mv config/config/database.example cd ..If you’re reading this, you’re probably contemplating a long painful process of getting your Rails app to a newer version.I followed this guideline in a project where I was upgrading from 3.2 to 4.2, and the final step from 4.1 to 4.2 was so easy that I was ready to deploy in less than 15 minutes.Before upgrading rails, it’s a good idea to upgrade other dependencies to make sure you have compatible versions of those gems.Edit: In this post we’re upgrading an application to Rails 5.0.0.beta1.1 and Rails 5.0.0.beta2 is now already released.Throughout this post we show some patches we needed to apply to Rails to get our application working.At any rate, following the upgrade guide and taking a look at the CHANGELOGs should be sufficient, although if you’re interested in seeing what’s currently happening, you can follow the day-to-day changes that are introduced in Rails.

If you’re looking for guides that cover upgrades to a specific version of Rails, you might want to refer to some of the articles listed below.

Make sure you have a decent suite of tests and they are all passing before you start with the upgrade.

If you’re on Rails 3.2, it is tempting to upgrade directly to Rails 4.2. Instead, upgrade first to 4.0.x, then 4.1.x, and finally 4.2.x.

That’s another way to understand what has changed between the versions.

Update the Gemfile with the newer version of Rails. so you might need to compare the diffs to make sure things like your mail configuration for production hasn’t been changed to the Rails defaults.

Leave a Reply