-
-
Notifications
You must be signed in to change notification settings - Fork 530
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
Drop worker_on_boot from puma config #992
Comments
Or even better, could we use the Heroku plugin mentioned here: https://github.com/puma/puma/blob/master/docs/plugins.md |
If puma/puma#1949 happens we may be able to drop our config file entirely |
Looking at this again, the puma configuration that comes with Rails by default now has us covered. We should drop our config entirely. |
composerinteralia
added a commit
that referenced
this issue
Feb 7, 2020
Closes #992 Rails now ships with Puma by default, including a default Puma config that already has everything we need. Co-authored-by: Frida Casas <frida@thoughtbot.com>
composerinteralia
added a commit
that referenced
this issue
Apr 6, 2020
Closes #992 Rails now ships with Puma by default, including a default Puma config that already has everything we need. Co-authored-by: Frida Casas <frida@thoughtbot.com>
composerinteralia
added a commit
that referenced
this issue
Apr 7, 2020
Closes #992 Rails now ships with Puma by default, including a default Puma config that already has everything we need. Co-authored-by: Frida Casas <frida@thoughtbot.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
rails/rails#31241 removed the advice to use
worker_on_boot
in config/puma.rb. I am guessing we can drop that now as well.The text was updated successfully, but these errors were encountered: