The "bundle show" will show that the gem is installed in the "bundle/gems"
directory.
But when we run from monit "bundle exec script/delayed_job" it complained
that it could not find it.

yes, we do have the .bundle/config and the BUNDLE_PATH to point to where the
.rvm stores the gems.

We spent the whole day trying things our and searching for answers on the
web... handful of such questions on stackoverflow but no definite answers.


But here is how we end up solving it....
we copied the gem source code into our project's vendor/gems directory
we have to do one more step to get the .specification file for the gem:  gem
specification attr_encrypted > .specification
in the Gemfile, we use the :path command -- gem "attr_encrypted", "1.2.0",
:path => "vendor/gems"

This solved our problem of the "bundle exec script/delayed_job" not seeing
the gem!


Thanks
Hock Sin




On Fri, Jun 3, 2011 at 2:50 PM, Ben Wanicur <[email protected]> wrote:

> What do you get when you run "bundle show" ?  Also, "bundle show <gemname>"
> will show you exactly where a gem is installed.
>
>
> On Thu, Jun 2, 2011 at 10:06 PM, Hock Yeoh <[email protected]> wrote:
>
>> Hi SDRuby,
>>
>> Need your help in figuring how to fix this.
>>
>> I'm using bundler to install this gem with this command line in the
>> Gemfile
>>    gem "attr_encrypted", "1.2.0", :git => "
>> http://github.com/shuber/attr_encrypted.git";
>>
>> I need to get the latest as it has fixes that the "released" version does
>> not have.
>>
>> Running "bundle install" will install the gem from the specified github.
>>  But when I "gem list" it does not show up.
>>
>> Apparently, it installs the gem in "ruby-1.8.7-p302/bundler/gems"  not the
>> regular directory "ruby-1.8.7-p302/gems"
>> - I'm using RVM.
>>
>>
>> Is there a way I can specify to the bundler to install it in the regular
>> directory?
>>
>> This is causing errors when I run "bundle exec script/delayed_job start".
>>  The log listed the attr_encrypted gem not found.
>>
>>
>> Thanks a million
>> Hock Sin
>>
>> Of course this problem goes away when I use the release gem (by
>> not specifying the :git in the Gemfile) and it installs the gem in the
>> regular directory !
>>
>> --
>> SD Ruby mailing list
>> [email protected]
>> http://groups.google.com/group/sdruby
>>
>
>  --
> SD Ruby mailing list
> [email protected]
> http://groups.google.com/group/sdruby
>

-- 
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby

Reply via email to