You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just wanted to give you guys a heads up I updated to 2.13.0, and it looks like it may have broke restarting puma on my production boxes.
I have a puma.rb file that defines where the pidfile lives. On production when I need to restart, I run: bin/pumactl -F config/puma.rb phased-restart, but now it seems that I may need to provide the PID manually since it doesn't read from the config file anymore?
Is this expected behaviour now? Or was I exploring something that was never really supported?
The text was updated successfully, but these errors were encountered:
I just wanted to give you guys a heads up I updated to 2.13.0, and it looks like it may have broke restarting puma on my production boxes.
I have a
puma.rb
file that defines where thepidfile
lives. On production when I need to restart, I run:bin/pumactl -F config/puma.rb phased-restart
, but now it seems that I may need to provide the PID manually since it doesn't read from the config file anymore?Is this expected behaviour now? Or was I exploring something that was never really supported?
The text was updated successfully, but these errors were encountered: