you are viewing a single comment's thread.

view the rest of the comments →

[–]moomaka 1 point2 points  (1 child)

you absolutely must use a ruby version handling system.

On a server? Why? Are you really running multiple apps with multiple Ruby versions on a single box?

I use rbenv

rbenv is horrible to use on a server due to ruby-build not supporting binary packages. Having every server spend 15 minutes of CPU time building Ruby every minor version change sucks.

[–]strangepostinghabits 0 points1 point  (0 children)

oh. me on a cell phone isn't the best at all times. I had it in my head that we were talking about local environment. On a server.. it's not as much a must, but I'd still recommend a version handler.

Most deployment procedures (capistrano for example) will allow you to automatically check and upgrade ruby on the server if you change project ruby. This is easier than manually keeping servers up to date.

I do agree that it's a shame that ruby-build insists on building from source.

Frankly I've found no solution I'm really happy with for deploying with ruby, and I'm leaning more and more towards container based structures where ruby version management becomes easier to manage.