Ruby on Rails

> On 2016-Apr-14, at 14:51 , Vince Laurent <lists@ruby-forum.com> wrote:
>
> "Have you checked the versions of all the gems (including rails) used
> on the old server and installed those and only those on the new one?"
>
> using gem list --local
>
> the old system has 16, the new one 64
> Here is the list of the differences:
>
> gem old new
> ------------------------------------
> actionmailer (2.3.5) (4.2.5)
> actionpack (2.3.5) (4.2.5)
> activerecord (2.3.5) (4.2.5)
> activesupport (2.3.5) (4.2.5)
> acts_as_ferret (0.4.8.2) (0.5.4)
> devise (1.0.5) na
> fastthread (1.0.7) na
> ferret (0.11.6) (0.11.8.6)
> jk-ferret (0.11.8.3) na
> passenger (2.2.11) (5.0.27, 5.0.26)
> rack (1.0.1) (1.6.4)
> rails (2.3.5) (4.2.5)
> warden (0.10.2) na
> will_paginate (2.3.12) na
>
> So... do I get rid of ALL the new gems and try to figure out how to just
> install the old ones?
>
> --
> Posted via http://www.ruby-forum.com/.

There is *a lot* of difference between Rails 2.3 and 4.2 (I know because I've recently helped a client do that "upgrade"†).

If your "old" application didn't use `bundler` (aka, does it have a `Gemfile` and `Gemfile.lock` in the top directory?), that might be the first tiny upgrade to make. Bundler did not exist when Rails 2.3 was current so it's not likely present unless someone introduced it.

At the very least, you could update rails to 2.3.18 (the last of its lineage). In a Gemfile, that would be:
gem 'rails', '~> 2.3'

The `will_paginate` gem does not support Rails 4 (unless that has changed somewhat recently). You might want to look at `kaminari` as a replacement for pagination.

-Rob

† it was actually a "full body transplant" rather than an "upgrade in place". We started with a bare Rails 4.2.x application and generated models as we went along, copying the relevant contents from the old application into the new. Same with controllers.

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/F6D785CD-3183-421C-AEDA-544547DDF5D4%40gmail.com.
For more options, visit https://groups.google.com/d/optout.