Hello,
I'm someone who uses RVM in production. I'll respond to the bits in
the thread that struck me:
* I don't know about now following the Unix way of things - we ended
up using a system wide install for RVM (set :rvm_type, :system
) so it's all in /usr/local. Is that not Unixy enough?
* The "waiting to hit y" thing is a bit of a furphy. You can automate
it in your capistrano deploy with something like: run "rvm rvmrc trust
#{release_path}"
* Also, I care deeply that production and development are as much the
same as possible to avoid the "it works on my machine" problem.
RVM certainly made it a bit harder to deploy but not very much. But I
think it's worth it because it locks down the separation and
deployment of gems and Ruby version (if nothing else) and like I said
similar production to development.
As for the bugs in RVM well this is pretty easy too because if you do
things in development/staging/continuous integration first you know
the bugs and rollback (or wait for a fix or whatever). You hit these
things very early.
On 28 July 2011 14:56, Dave Bolton <[email protected]> wrote:
>>> You could install both, make sure one has a suffix set (so ruby becomes
>>> ruby19, irb becomes irb19, etc).
>>
>> Didn't know about that.
>> Won't it break stuff because we'd have to use explicitly 'ruby19' instead
>> just 'ruby'?
>
> And then, you could create some nifty shell scripts that manage your
> per-instance environment settings, and then ... oh.
>
> For the record, I think Ben nailed it before -- big environments
> should be an app per server, or at least a Ruby per server if more
> than one app is on there, while smaller apps could either be a VPS
> each, or put the effort into RVM. Here at Westfield we're one app or
> Ruby per server. Like Michael said earlier, when you've got a
> multitude of environments it can get really hairy (we were stuck on
> ancient versions of Ruby for a while because of this), so the less
> moving parts the better.
>
> Cheers,
> Dave
>
> --
> 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.
