You can use ENV vars to config default bundler behavior. Here is my solution of this problem: http://chipiga.pp.ua/ruby/bundler-on-heroku-and-without-feature/
On Sep 5, 2:29 am, Gabriel <[email protected]> wrote: > It seems like you could use bundle groups and then use 'bundle package > --without dev_test_gems' to create a local cache of just your > production gem dependencies. Remember to check your Gemfile.lock file > into git and then git push to heroku. > > Heroku will then use 'bundle install --deployment' which will look at > your Gemfile.lock to determine which gems to install from vendor/ > cache. > > Again, I haven't tried this. It just seems like it might work. > > G'luck! > > Gabriel > > On Sep 3, 4:55 am, Ashley Moran <[email protected]> wrote: > > > > > On 1 Sep 2010, at 06:42, Gabriel wrote: > > > > Maybe I'm missing something obvious, but can't you specify a group for > > > those gems and then only deploy them in dev and test? So as part of > > > your deployment to heroku you'd do something like: bundle install -- > > > without gems_heroku_dun_like > > > > I'm going to have to deal with exactly the same problem so I'm curious > > > if this will work for you. > > > Hi Gabriel > > > Interesting idea, but how do you tell Heroku which Gemfile groups to > > bundle? I didn't think that was possible. > > > Cheers > > Ash > > > --http://www.patchspace.co.uk/http://www.linkedin.com/in/ashleymoran -- You received this message because you are subscribed to the Google Groups "Heroku" 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/heroku?hl=en.
