Richard Schneeman
Richard Schneeman
Wouldn't all default config vars fall into the same trap here?
Related support ticket: https://heroku.support/708919
This version in the path actually comes directly from building a Ruby binary, it's not something that Heroku is specifically doing. One way to possibly "solve" the issue is to...
In the CNB we install that exact version of bundler captured in the Gemfile.lock https://github.com/heroku/buildpacks-ruby It might make sense to backport that behavior here and deprecate the current "blessed version"...
This came up in ticket 1264615 (internal link)
Deployed https://devcenter.heroku.com/changelog-items/2912
Right now rails runner not being able to execute is treated as "we couldn't get enough information" to know what to do. But I do think it's a good indicator...
> How would this work 🤔 Is there an easy way to determine whether an application is new or not? We've got that baked in. Check out `new_app?` in the...
If you want to do this manually instead of automatically you can hook into `rake assets:precompile` for example: ``` Rake::Task["assets:precompile"].enhance do Rake::Task["db:migrate"].invoke Rake::Task["db:schema:cache:dump"].invoke end ``` Then you also need to...
> If db:migrate is executed during precompile instead of release phase, then a bad migration can't prevent the release from becoming live. This guarantees the atomicity of those actions happening...