# GitHub and continuosly upgrading Rails

**URL:** <https://www.ruby-forum.com/t/github-and-continuosly-upgrading-rails/263771>\
**Category:** Uncategorized\
**Created:** [April 7, 2023, 11:14pm UTC](https://www.ruby-forum.com/t/github-and-continuosly-upgrading-rails/263771 "2023-04-07T23:14:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jgomo3](https://www.ruby-forum.com/user_avatar/www.ruby-forum.com/jgomo3/32/950_2.png) [@jgomo3](https://www.ruby-forum.com/u/jgomo3)\
**Post date:** [April 7, 2023, 11:14pm UTC](https://www.ruby-forum.com/t/github-and-continuosly-upgrading-rails/263771/1 "2023-04-07T23:14:55Z")

</div>

GitHub is a Monolith made in Ruby on Rails.

In their latest blog entry, GitHub engineers explain how they keep Ruby and Rails up to date.

> **[Building GitHub with Ruby and Rails | The GitHub Blog](https://github.blog/2023-04-06-building-github-with-ruby-and-rails/)**
>
> Since the beginning, GitHub.com has been a Ruby on Rails monolith. Today, the application is nearly two million lines of code and more than 1,000 engineers collaborate on it daily. We deploy as often as 20 times a day, and nearly every week one of...

---

<div class="post-metadata">

**Author:** ![AndyMaleh](https://www.ruby-forum.com/user_avatar/www.ruby-forum.com/andymaleh/32/2475_2.png) [@AndyMaleh](https://www.ruby-forum.com/u/AndyMaleh)\
**Post date:** [April 11, 2023, 5:45pm UTC](https://www.ruby-forum.com/t/github-and-continuosly-upgrading-rails/263771/3 "2023-04-11T17:45:36Z")

</div>

That’s a bit extreme and not recommended for simple Rails shops. Staying on the cutting edge is usually only useful to committers and contributors, but is too risky for actual business websites (GitHub must be rich enough to handle the cost of staying on the cutting edge with issues popping up every now and then). In any case, it is certainly recommended for standard business websites to stay up-to-date with final versions of Rails whenever possible. But, it is OK to be a major version behind at most in actual business apps. That gives Rails time to iron out issues in new releases before upgrading to them.

Either way, it’s interesting to learn from the GitHub folks.

Thank you for sharing.