Today, I ran these commands:
sudo monit stop all sudo apache2ctl stop ps -eaf | grep runtime rm -rf .rvm sudo rm -rf /etc/profile.d/rvm.sh /usr/local/rvm /usr/local/bin/rvm* exit
And then I bounced around my office manically and ate popcorn.
You see, we've been using
rvm to manage our production ruby install,
and it just never worked well. Sure, it installed ruby fine, but then
it would change it's api, and beat up my shell, and generally
making a pest of itself.
Unfortunately, every time I ran into a problem, I never had the time to
rvm. Instead I'd patch around it. But this week, having
encountered a second fork bomb, I decided enough was enough, and I
took the time to throw it off the island.
I am not the only person to have discovered some of the problems with rvm. There's a really promising looking rbenv and it's sister project ruby-build. I wanted something simple, and tried to leverage those.
We have a bunch of competing needs, and eventually I came to this design.
- ruby would be built into
- passenger would use that path explicitly
- The daemons that I start, can have their
- humans trying to do things will be inconvenienced.
- chef will keep driving.
- leverage ruby-build for the build process.
- Do not try to use rbenv, it doesn't add much over chef here.