"Hey fellow devs, I've been working on an old Rails project that's still rocking some ancient gems, and I'm thinking it's time to give it a modern makeover. Has anyone else been in this situation and what was your strategy for migrating to newer, more efficient gems? Looking for advice on how to balance backwards compatibility with keeping up with the latest and greatest."
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
"Ruby on Rails: Migrating to Modern Gems - What's the Best Approach?"
- Thread starter mgertsik
- Start date
"Lol, I feel you guys. I just did a major migration from Rails 5 to 7 last year and it was a beast. If you're still on old gems, just update to the latest and make sure your dependencies are sorted, it'll make the migration smoother."
mila_sunshine
New member
- Joined
- Aug 23, 2013
- Messages
- 3
- Reaction score
- 0
"Hey guys, I'm still rocking Rails 5.2 at work, but we're planning to migrate to the latest version soon. From what I've gathered, it's all about removing outdated gems and replacing them with more modern alternatives like ActiveStorage and ActionCable."
"Hey guys, I've been in a similar situation before, and I found it helpful to start by auditing your existing codebase for gems that are no longer maintained. You can then create a list of priorities for updating/ replacing those gems. Has anyone had experience with the 'dry-rb' suite for this kind of task?"
"Been in a similar situation with an old Rails app and had to upgrade the gems. My advice would be to start by identifying the most critical dependencies that need to be updated, then work your way down the list. Also, make sure to test in isolation before applying the changes to the live app."
макмилан678
New member
- Joined
- Jan 22, 2018
- Messages
- 3
- Reaction score
- 0
Discussion: best practices
gandjubas47
New member
- Joined
- Jul 16, 2013
- Messages
- 2
- Reaction score
- 0
Discussion: latest news
I've done some migrations from old gems to new ones in Rails and it always depends on the specific gem. If it's a widely used one like devise or activeadmin, it's usually pretty straightforward, but if it's a custom or less popular gem, it can get hairy. Has anyone tried using something like rubocop to identify gems that need updating?
"Yeah, I've been in a similar situation and decided to migrate to Rails 7. I followed a guide that suggested updating gems one by one, starting with the most critical ones. It was a long process, but it's been worth it, especially with the added security features."