Installing on OS Catalina

I am reading ahead in the install page ~/installation/macOS/ and it says " On Mojave (10.14) Because of SIP Protections in Mojave, you must run:…"

Now that the OS is Catalina, are there any new things that need to be done at that stage?

Also on that page it says " We strongly recommend against installing Ruby gems globally to avoid file permissions problems and using sudo ." If I am cd into my directory in Terminal, am I right in thinking that I am not in danger of installing Ruby gems globally?

I cant personally speak to the first part, as I my setup was created pre Mojave, so the easier version for me applied. I dont think anyone on my team has run into any Catalina specific problems on reinstalling after a wipe.

As for the second half, I would suggest going the rbenv route to install ruby, (per the "setup rbenv" instructions on that page), so when you do your bundle install, the gems install only for rbenv’s ruby (not the system ruby) , and also only THAT version of rbenv-ruby.

Anytime you can avoid touching or messing with any of the native MacOS ruby parts (either due to security or just how out of date they are) you will save a lot of problems.

Thanks. I will take a look.

I see a warning and not sure what this signifies? Or what I should do?

WARNING: You don’t have /Users/myname/.gem/ruby/2.6.0/bin in your PATH,
gem executables will not run.
Successfully installed bundler-2.1.4
Parsing documentation for bundler-2.1.4
Installing ri documentation for bundler-2.1.4
Done installing documentation for bundler after 3 seconds

I have got past that.

1 Like

Do you still need help with this issue?

Did you add that directory to your PATH statement?

I went through the Catalina upgrade and wrote about the approach that worked for me to get ruby and bundler working. In addition I had to delete and rebuild all my vendor directories in my projects as the previous OS version 2.3 ruby is no longer available.

1 Like

My question was similar to OP’s. I resurrect this b/c w/Big Sur now too, it might be time to update the guidance for Mojave /and forward/?

@MichaelCurrin, this was useful, but I had to dig a bit to find it. For anyone else who follows, try instead