Part of it might centre around not knowing the tool very well, but then that's the whole point. A production setup should be as simple as it can possibly be (and no simpler). In production, RVM is accidental complexity.
I don't think it's a matter of "I feel it's wrong". It's that I don't want my production ruby runtime to rely on a large set of bash scripts that are prohibitively hard to properly understand or debug quickly. As soon as you include RVM, you have a bunch of environment-related complexity that wasn't there before, and unless you're using multiple rubies on one server, it's complexity for no gain. —Ben On 28/07/2011, at 11:56 AM, Julio Cesar Ody wrote: > I think you think so because, as you put it, you're a newcomer to RVM. > There's a lot of ifs which may or may not apply to the server you're > running your applications on. > > I know more developers who write Ruby based on the install they have > locally on their machines than developers who know the difference. Are > you running apps on your server that rely on language features that > match the ones you have on your development machines? If yes, then you > just don't need it. Granted, it's unlikely you'll run a bunch of Ruby > apps, each using a different version of Ruby, on the same server. But > the answer to your question depends on whether that's the case or not. > > I use RVM on a VM I run my website and a couple of other things. It's > all Ruby 1.9. I don't really need it. It has never gotten in the way > anyway. Just rather have my rubies and gems sandboxes away from each > other. > > > P.S.: it's probably not flawless, but reasons not to use RVM in > production more often than not come down to "I feel it's wrong". The > rest seems to circle around not knowing the tool too well. > > > > > On Thu, Jul 28, 2011 at 11:43 AM, Mike Bailey <[email protected]> wrote: >> It occurred to me that RVM *could* result in ops guys feeling like the >> waiter in LA Story. >> http://youtu.be/z-CrML0BzOA >> "I'll have a half double decaffeinated half caf with a twist of lemon" >> While RVM is great for developer workstations, to me it doesn't seem right >> for production environments. A slightly longer explanation of my reasoning >> is here: http://mike.bailey.net.au/2011/07/rvm-in-production/ >> What are your experiences? >> >> - Mike >> >> e. [email protected] >> >> w. mike.bailey.net.au >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Ruby or Rails Oceania" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/rails-oceania?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Ruby or Rails Oceania" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/rails-oceania?hl=en. > -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
