2 ms·
I'd say it's worth doing, unless you intend to spin down the app entirely in a couple of years, just for the sake of security updates. You don't want to be in a
by ufmace 7y ago
I'd say it's worth doing, unless you intend to spin down the app entirely in a couple of years, just for the sake of security updates. You don't want to be in a situation where there's a vulnerability announced, and you can't pick up a fix without updating 6 versions, with all of the headaches that brings. It's worth devoting a few % of time here and there to bumping everything to the latest version and fixing any issues that come up, and maybe trying to move things that had been using external gems to any new internal processes that cover the same tasks.
- SnowingXIV 7y agoGood point. It's an app that's got a life left to it. Not much in the way of changes but it's a pretty critical piece of software. Cloned a copy, moving it to 5.2 and 6.0. Had to update ruby to 2.5.1. Looks like postgresql (which I use heavily) is also making comments about migrating data. This is not seamless. Lots of issues not to mention `rails app:update` basically wipes out the files, you go back in replace with needed info via diff, more errors. I thought that was supposed to alleviate that. If this works I'm hoping at least pushing to Heroku will handle that part. Heroku notes the gem file and makes the required updates.