Running TOP locally: Is recommended setting of rbenv to 3.1.2 still necessary?

[Breadpaw]

When installing TOP locally, I ran into the following comment in the instructions:

Note: If bundle install doesn't work and you get a "rbenv version" error of some kind, try running the following command to set your Ruby version in the project.

rbenv local 3.1.2

Link to the page and section

My question: The TOP installation guide currently instructs to install and globally set Ruby version 3.2.2. Does this make this comment unnecessary?

[KevinMulhern]

Nice catch! thanks @Breadpaw 💪 I've updated the version. You have a point about it being unnecessary. It might be good to keep around as a guard rail for anyone that has Ruby installed and goes straight into the setting up locally guide. But I need to think on that more.

[Breadpaw]

Thanks @KevinMulhern , also for the quick reply :)

I considered suggesting a comment in this section for people to consider updating Ruby via the Installing Ruby lesson for their respective system. Just a highlight, so that long-time or returning students are reminded of their possible earlier installs of Ruby (as was the case with my system)

[KevinMulhern]

Thinking about this a bit more, the Ruby version used on the site and on the curriculum don't always match. When a new version of Ruby comes out, we update the curriculum fairly quickly. But theres usually a lag time between the new versions release and the dependencies we use on the site getting updates to support it. From how thats played out in the past, it could be anywhere from a few months to a year before we can safely update and be running the site on the same version used in the curriculum.

I think we should continue linking to the install guide lesson, it's a good general guide. But have a new step in the Install Gems and Migrate the Database section advising contributors to check they have the correct Ruby version installed. The source of truth for that will always be in our .ruby-version file.

Thanks again, for raising this @Breadpaw. This has probably caught more than a few people out when we've been between versions in the past.