4 ms·
I saw a comment that stuck with me once: "Ruby people don't get root", referring to an unwillingness to trust Ruby tools or the ruby community as it got closer
by theonemind 4y ago
I saw a comment that stuck with me once: "Ruby people don't get root", referring to an unwillingness to trust Ruby tools or the ruby community as it got closer to his system.
This rule works surprisingly well.
- treeman79 4y agoIts good Practice to never use root for any ruby application. RVM or rbenv with Gemfile do a great job in giving you any version you need and keeping the system clean. Way back in the day you basically had to reverse engineer each developers environment to let another person use it. Now it’s common to grab any semi decent project and be up in running in a couple minutes. Brew usually takes care of any system level stuff. Nokogiri, image magic, etc.
- NegativeLatency 4y agoeven just ‘gem install PACKAGE —-user’ will get you pretty far
- skunkworker 4y agoI don’t think I’ve touched system ruby in years. With RVM everything is just installed into my home ~/.rvm folder and keeps it tidy.
- marcosdumay 4y agoI try not to use anything in PHP; Python and Ruby are isolated as well as possible (optimally, not having access to my homedir and definitively not getting "installed"); Bash will get thoroughly reviewed for data validation red flags; and I will avoid anything that imposes a code convention and is written in Go. Now I am surprised that I don't have any general rule for C and Java.
- KerrAvon 4y agoFirst rule of Unix security is that no tool should have unnecessary root. Ruby isn’t special in this regard, and Homebrew doesn’t particularly seem to be problematic. I’ve had a lot bigger problems with Python-based tooling, tbh, but I imagine it’s the developers and not the language.