On Jul 25, 2008, at 08:09 AM, Rob Mauchel wrote:
> Eric Hodel wrote:
>> On Jul 24, 2008, at 11:05 AM, Rob Mauchel wrote:
>>> So, in the end, you were right Eric! (Though it wasn't necessary,
>>> for me
>>> at least, to set GEM_HOME to anything, presumably because the CPanel
>>> Ruby Gem Installer takes care of that.)
>>
>> I recommend setting GEM_HOME so you don't have to think about what
>> `gem install` will try to do.  It is not used for activating gems.
>
> Sorry, but I think you're missing my point. I don't have the  
> privileges
> to open a terminal on the server (instead using CPanel's UI for
> configuring the CronJob I referred to at the beginning of this topic
> discussion), so I don't/wouldn't manually run 'gem install' on the
> server manually/directly. CPanel's Gem Installer is pre-configured  
> with
> UI that allows you to see what gems are installed in the web server's
> global repository and only allows you to install new gems into your
> personal local repository.

Oh, ok, that's pretty neat!