> On Aug 22, 2018, at 8:08 AM, Hassan Schroeder <
hassan.s...@gmail.com> wrote:
>
> On Wed, Aug 22, 2018 at 6:30 AM, Robert Nicholson
> <
robert.n...@gmail.com> wrote:
>
>> 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
>
>> Are there any migration guides that highlight the complexity involved?
>
> π±π±π±π±π±π±π±π±π±π±π±π±π±
>
> Your options:
>
> 1) migrate (very slowly) version-by-version
>
> 2) "big bang" re-implement the entire app on the current Ruby/Rails
>
> 3) continue running the old version and start replacing it piecemeal
> (the "Strangler Pattern")
>
> Good luck!
LOL, well said. I wouldn't recommend #1, imho. A lot of extra work to get to the end. Just rewrite, or let things be as they were. Upgrading Apache and Passenger probably aren't going to impact the migration of the app. A newer Ruby *might* require some updates in the app (but give speed improvements). Keeping on the old Rails and otherwise old app code probably would still work in the new environment (albeit, there could be security concerns).