-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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 & symlinks doesn't change destination folder? #3290
Comments
Looks like that yes, but is your new application code loaded or not? Please test Docs says symlinks are evaluated, so if new code isn't being loaded, this is a regression, but it might be that the state isn't being reflected correctly (in that state file, in the worker process titles). |
it's seem like application run on newest. But how can I show the newest state of puma? |
It's a bug in regards to the things I mentioned above. Please dive into the Puma code base and see if you can come up with a fix. This is not a support forum :) |
My puma config
current symlink
after pharsed-restart
its seem like puma still working on old release folder?
The text was updated successfully, but these errors were encountered: