Keep Rails Upgraded

Lucky you, it's time to upgrade Rails versions! I know, you just upgraded your app a few years ago, but it's time again. The good news is that you've got a team of "professionals" to help make the process a bit smoother.

We'll start this workshop by working together to upgrade an existing Rails 4 application to Rails 5. We will highlight some common pitfalls and then we'll work as a group to kickstart your own app upgrade.

Why suffer alone? Join us for this Rails upgrading workshop and you'll have a community of support from fellow upgraders, Rails contributors, and Ruby Heroes.

Transcript

1. KEEP RAILS UPGRADED
2. DEREK PRIOR
3. RICHARD SCHNEEMAN
4. CALEB THOMPSON
5. EVERYONE ELSE
6. HOMEWORK
7. github.com/derekprior/lobsters
8. AGENDA
9. WORDS OF UPGRADING WISDOM
10. GROUP LIVE CODING
11. ADDITIONAL RAILS 5 CONCERNS
12. UPGRADE YOUR APP WITH OUR HELP
13. WHY?
14. HOW?
15. BEFORE YOU UPGRADE
16. CLEAN SUITE
17. RUBY 2.3
18. UPDATE YOUR BUNDLE
19. bundle outdated
20. bundle update
21. bundle update scenic
23. READ THE DOCS
24. READY TO UPGRADE > Clean Suite > Latest Ruby > Updated Bundle > Documentation Read
27. OTHER PROBLEMS
28. PARAMS IS NOT A HASH
29. to_h WILL RETURN A HASH
30. to_unsafe_h WILL GIVE YOU ALL PARAMETERS
31. CALLBACKS DON'T STOP WITH FALSE
32. throw :abort TO HALT CALLBACK CHAINS
33. CONTROLLER TESTING EXTRACTED
34. ASSIGNS, TEMPLATE TESTING REMOVED
35. NOW LIVE IN rails-controller-testing GEM
36. content_tag_for AND div_for EXTRACTED
37. record_tag_helper GEM
38. ApplicationRecord
39. SIMILAR USE-CASE TO ApplicationController
40. APP-SPECIFIC EXTENSIONS FOR DATABASE-BACKED MODELS
41. KEEPS FROM MONKEY-PATCHING ActiveRecord::Base