Two Commonly Used Rails Upgrade Strategies

28/05/2020
1.169

Rails upgrades can be done in many different ways. Depending on the application that you want to upgrade, some ways make more sense than others. There are factors that determine which Rails upgrade strategy is the best for your case, like how big your application is, or how frequently changes are pushed to the master branch. In this article I'll be covering two common Rails Upgrade strategies so you can decide which one is the best for your application.One important note before starting: We highly recommend not skipping any Rails version while upgrading. If your goal is to get to Rails 6.0, and you are in 5.0, make sure to first upgrade to 5.1 and then to 5.2. Each minor version of Rails provides deprecation warnings for the next version. If you skip versions you'll find unexpected errors in your app that will be hard to debug. Some people have used a strategy that does many version jumps at once. This radical approach makes sense only when your Rails application is very small.
Two Commonly Used Rails Upgrade Strategies #ruby #rubydeveloper #rubyonrails #upgrade https://rubyonrails.ba/single/two-commonly-used-rails-upgrade-strategies