Re: exclusion of bundler gems (via group, :platforms, what else?)
No worries, Orlin -- we pushed it live in November, IIRC, and publicized it via Twitter and the December newsletter. We're still figuring out how best to let the community know when changes like this happen. Ben On Jan 24, 9:31 am, orlin wrote: > Thanks Ben. Should have looked at the docs again. First time seeing this, > I guess the exclusion feature is relatively new. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: exclusion of bundler gems (via group, :platforms, what else?)
Thanks Ben. Should have looked at the docs again. First time seeing this, I guess the exclusion feature is relatively new. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: exclusion of bundler gems (via group, :platforms, what else?)
Hi Orlin, You can exclude your development and test groups. Take a look at http://docs.heroku.com/bundler#specifying-gems-amp-groups Ben On Jan 24, 5:55 am, orlin wrote: > I have to start things with `bundle exec` and put all the gems I use in the > Gemfile. However some gems are incompatible with Heroku (those specifically > for mac-osx) and make it impossible to deploy the app. It would be great if > there is a way to exclude certain :development & :test groups when pushing > to Heroku. Those gems aren't used in production anyway. It would make the > slugs leaner too. The platforms tag isn't helping either. There is no > :platforms => :osx. The only workaround I see so far is to develop with > :ruby_18 and deploy to :ruby_19. The 1.8 is still useful for capybara-envjs > but 1.9 is obviously preferable... > > Orlin -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
exclusion of bundler gems (via group, :platforms, what else?)
I have to start things with `bundle exec` and put all the gems I use in the Gemfile. However some gems are incompatible with Heroku (those specifically for mac-osx) and make it impossible to deploy the app. It would be great if there is a way to exclude certain :development & :test groups when pushing to Heroku. Those gems aren't used in production anyway. It would make the slugs leaner too. The platforms tag isn't helping either. There is no :platforms => :osx. The only workaround I see so far is to develop with :ruby_18 and deploy to :ruby_19. The 1.8 is still useful for capybara-envjs but 1.9 is obviously preferable... Orlin -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
