-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Only add default web dyno if config.ru
exists
#1355
Comments
Thanks a ton for the issue. I would accept this change. |
dentarg
added a commit
to 84codes/heroku-buildpack-ruby
that referenced
this issue
Feb 22, 2023
Temporary workaround for heroku/heroku-buildpack-ruby#1355
walro
pushed a commit
to 84codes/heroku-buildpack-ruby
that referenced
this issue
Sep 25, 2024
Temporary workaround for heroku/heroku-buildpack-ruby#1355
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
You could have an app that is not an web app, but for whatever reasons, it has
rack
as a dependency. Then, the buildpack would automatically add aweb
dyno to that app when it is deployed for the first time (maybe you do some automated testing with Terraform)heroku-buildpack-ruby/lib/language_pack/rack.rb
Lines 9 to 11 in 104fe3a
I discussed changing this with @schneems at https://ruby.social/@Schneems/109514562198812396
The text was updated successfully, but these errors were encountered: