My solution has been to check the gem as a submodule into vendor/engines gem 'mygem', '0.0.0', :path => 'vendor/engines/mygem'
I do a git init submodule && git update submodule in the capfile for deployment. This works OK for my use case but it also has it's painful spots. Bundler really ought to have a better solution for this. I like the idea of a hostname based solution where each developer (and possibly each server) could have a different set of gems from different locations. -- 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.
