Skip to content
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

Using a config file with pumactl and 2.13.0 #764

Closed
keithpitt opened this issue Aug 15, 2015 · 2 comments
Closed

Using a config file with pumactl and 2.13.0 #764

keithpitt opened this issue Aug 15, 2015 · 2 comments

Comments

@keithpitt
Copy link

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?

@evanphx
Copy link
Member

evanphx commented Aug 15, 2015

Sorry about that! Should be fixed now.

@keithpitt
Copy link
Author

Thanks @evanphx! 💟

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants