How we upgraded an obsolete Ruby on Rails application with lots of legacy code (part 1)
Captain's log, stardate d604.y36/AB
As a development consultancy, we deal with a whole lot of projects: static websites, web platforms, intranets, mobile apps, etc. Some are bigger, and some are smaller, but all of them require maintenance.
This post is the first one of a series where we break down how to correctly upgrade a Ruby on Rails application.
In this first part, I am going to introduce you to the project and how we planned the upgrade minimising risks because the project is already live.