Handling redployments about sanic HOT 2 CLOSED

Hmm, Sanic is set up to properly drain connections on close, but does not support reloading, so you would have to do what you outlined. Looking at Gunicorn, it looks like it creates an arbiter before loading any application code. To create workers, the arbiter forks the process first, then initializes the application code to allow graceful reloading. Pretty neat.

We should be able to support that paradigm by shifting to running apps with python -m sanic file.app (currently supported) when using multiple workers. I think I'd like to add this, but I'm not sure when I will be able to get to it, so I'm tagging in case someone else wants to pick it up first :).

from sanic.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this is incorrect, please respond with an update. Thank you for your contributions.

from sanic.