I've been curious why heroku deploys my development and test gems onto my production machine. In the latest newsletter they mention adding the following line to prevent that from happening. My question is, "why isn't this the default behavior?"
"heroku config:add BUNDLE_WITHOUT=development:test" >From the newsletter..... Specify gems to bundle in production Is your slug getting too big? Taking too long to compile? One of the most common reasons for that is a bloated Gemfile. There's no reason to include the gems from your development and test groups when you push to Heroku, so you can exclude them by setting a config var: $ heroku config:add BUNDLE_WITHOUT=development:test Once that's added, future deploys will automatically ignore gems in the development and test groups—or whatever other groups you want to exclude. -- 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.
