*headdesk*

I really should have kept IRC / twitter logs of my arguments with him.

Let me count the ways:

   - he recommends that you always use the absolute latest version, locking
   to a particular 'stable' version is discouraged
   - one time, he switched to Rubygems 1.6.2 because "somebody on IRC said
   it worked best", which broke Ruby 1.9.2 installs (or 1.8.7, I forget)
   - default gemsets for JRuby broke JRuby 1.4 OpenSSL (which we were locked
   to for some time, our fault, but unavoidable)
   - he changed the way that the system-wide install works with little to no
   advance notice, meaning our puppet image creation simply broke one day
   - .rvmrc causes prompts by default. If you check .rvmrc into your repo,
   and then cd into that directory, your automated process will hang. Oh, and
   it won't create a gemset automatically if one is specified. I ended up
   putting "rm -f .rvmrc" into our deployment script.
   - You can't override some .rvmrc stuff on a system-wide basis
   - He discourages people 'packaging' RVM installs to work around these
   issues

RVM is great for development, but good luck using it in any kind of
automated production environment.

On Thu, Jul 28, 2011 at 11:50 AM, Andrew Grimm <[email protected]>wrote:

> Wayne E Seguin, the creator of RVM, said on SO that it was actually
> designed for production
>
> http://stackoverflow.com/questions/5864001/is-rvm-production-ready/6282260#6282260
>
> I humbly disagreed at
>
> http://stackoverflow.com/questions/5864001/is-rvm-production-ready/6286677#6286677
>
> Still, it's more production-ready than bumblebee!
>
> Andrew
>
> On Thu, Jul 28, 2011 at 11:45 AM, Ben Hoskings <[email protected]> wrote:
> > I agree, I think RVM is fundamentally not suited to production. That is,
> I think the things that make it a useful tool are exactly the kinds of
> things you don't want in production.
> >
> > I build from source. `babushka benhoskings:ruby19.src` :)
> >
> > —Ben
> >
> >
> > On 28/07/2011, at 11:43 AM, Mike Bailey 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.
>
>


-- 
Michael Pearson
The Bon Scotts; http://www.thebonscotts.com

-- 
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.

Reply via email to