[close #358] Fail on Rake detect for Rails AppsRails applications should be reasonably expected to run `rake` when a Rakefile is present.
Right now this is the behavior we support https://github.com/heroku/heroku-buildpack-ruby/issues/358#issuecomment-90250883. While it might be reasonable that a Ruby application might not expect us to run Rake, a Rails app with the asset pipeline, while they might not be using the asset pipeline, should b...
Alternative to #463 always warn on Bundler changeWarn when upgrading bundler version. Instead of trying to detect errors or problems make the fact that we upgraded bundler much more noticeable. This may result in more false flag support ticketes but it also points people to how to test their app to ensure the problem was not in-fact caused by the bundler version change by setting the release version on their app.
This warning will only be pr...
Platform changes prevent unacceptable env varsDue to platform changes we can no longer set weird env var names. This test was for a very intermittent problem not likely to reproduce again, we can safely get rid of this test for now and reintroduce if needed.
Originally introduced in
- https://github.com/heroku/heroku-buildpack-ruby/pull/229
- https://github.com/heroku/heroku-buildpack-ruby/commit/8b6126f1497a85dff8b897bf0426b5d8333c6d7f
Warn on no Procfile use, don't mention WebrickWhile someone __may__ be using webrick they may also be puma or some other webserver with an integrated rack handler. Make the error more generic. The webpage was updated to say that a `Procfile` is best practice. It still talks about WEBrick but this is secondary.
change default ruby to 2.2.4 from 2.0.0Ruby 2.0.0 is being sunset on Feb. 24, 2016. This changes the default
for new apps that haven't set a ruby in their Gemfile. By doing so, we
won't be putting users on a Ruby being sunset soon.
In addition to Ruby being sunset, Rails 5 beta needs a newer Ruby as
well.
Richard Schneeman
Matt Graham
Damien Mathieu
Terence Lee
Joe Kutner
Rico Sta. Cruz