-
Notifications
You must be signed in to change notification settings - Fork 302
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
Phased restart #329
Phased restart #329
Conversation
Any predictions about when this pull request will be accepted? |
I agree with this PR. |
We need this PR also! |
@mksvdmtr Will have this released this week. can you rebase this PR ? |
e92af03
to
7f954be
Compare
7f954be
to
6e068a4
Compare
I will release a beta version now. Let me know if you find any regression. |
@seuros Is there any interest in making this new behavior configurable? Some arguments against this new behavior:
I think it's a good idea to support phased restarts. But I believe that shouldn't be the default as it requires much more work and insight, and introduces more issues if not aware of it. I would therefore suggest to revert the default back to a puma hot restart. For those who need zero downtime deployments, they could enable a configuration option to activate it. What are your thoughts about this? |
@phylor yes. I agree with you . |
Added the ability to phased restart puma
Need to define a release directory in config/puma.rb:
directory '/var/www/current'
Otherwise, Puma won't pick up your new changes when running phased restarts