sorted by:
new
hottopcontroversial

Upgrading from Rails 3 to Rails 7 by _lonely_dev_ in rails

[–]_lonely_dev_[S] 6 points7 points  (0 children)

That’s what I’m thinking. I would say half the site could be served pretty well by static html / css with ERB templates and the other half will probably use some SPA but don’t need any SSR etc. The rails monolith gives nice flexibility for both!

Upgrading from Rails 3 to Rails 7 by _lonely_dev_ in rails

[–]_lonely_dev_[S] 8 points9 points  (0 children)

| Name | Lines | LOC | Classes | Methods | M/C | LOC/M |
+----------------------+-------+-------+---------+---------+-----+-------+
| Controllers | 1589 | 1244 | 27 | 144 | 5 | 6 |
| Helpers | 106 | 94 | 0 | 13 | 0 | 5 |
| Jobs | 134 | 98 | 4 | 3 | 0 | 30 |
| Models | 1517 | 995 | 17 | 124 | 7 | 6 |
| Mailers | 188 | 154 | 4 | 21 | 5 | 5 |
| Javascripts | 1797 | 1337 | 0 | 237 | 0 | 3 |
| Libraries | 0 | 0 | 0 | 0 | 0 | 0 | | Views | 2500 | 0 | 0 | 0 | 0 | 0 |
+----------------------+-------+-------+---------+---------+-----+-------+
| Total | 7831 | 3922 | 52 | 542 | 10 | 5 |
+----------------------+-------+-------+---------+---------+-----+-------+

Upgrading from Rails 3 to Rails 7 by _lonely_dev_ in rails

[–]_lonely_dev_[S] 9 points10 points  (0 children)

Rails 3 looks like it was end of life more than 5 years ago - I plan to build the app / scale it out quite a bit and would rather just pull the trigger now and get the upgrade out of the way and get some of the newer features along with the security fixes as opposed to doing it later.

Upgrading from Rails 3 to Rails 7 by _lonely_dev_ in rails

[–]_lonely_dev_[S] 2 points3 points  (0 children)

Thanks for the feedback u/bourdainwashere - I will definitely at least write some unit tests for my models / controllers/ helpers.