Thursday, August 23, 2018
the main change here is the rails version.
-- Once you figure out the update requirements for that - the apache / ruby / passenger changes are (probably) a non-issue.
On Wednesday, 22 August 2018 14:30:34 UTC+1, Robert Nicholson wrote:
the key question is whether you have test coverage on the original app. If you do, then I'd be tempted to do a big-bang update.
fire it up in a development environment, upgrade all the gems (things are going to break anyway - so no point in fighting the gem battle separately from the rails battle).
then run your tests and see what happens.
odds are that 95% of the changes will be handled in the upgrade guide with things like params handling.
you'll also need a 2-3 upgrade guide!
https://medium.com/ruby-on-rails/upgrading-a-rails-2-app-to-rails-3-d25c7b390fa1
On Wednesday, 22 August 2018 14:30:34 UTC+1, Robert Nicholson wrote:
We have a rails application that's been running on an old version of Rehat 4.
We have to move it to Redhat 7
It was
apache 2.2.4, ruby 1.8.7, rails 2.3.8, passenger 2.2.5
and we're expected to migrate to
apache 2.4.27, ruby 2.51, rails 5.2.1 and passenger 5.3.4
This application used gems like
search logic
will_paginate
composite_primary_keys
to name a few.
…..
Are there any migration guides that highlight the complexity involved?
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/b58b474f-7d8f-493d-b6a1-5ece0f0df0d9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment