-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
uWSGI Support #972
base: development
Are you sure you want to change the base?
uWSGI Support #972
Conversation
@@ -201,4 +204,4 @@ def autoproxy( | |||
) | |||
|
|||
cherrypy.server.start() | |||
cherrypy.server.wait() | |||
#cherrypy.server.wait() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the purpose of these changes?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I found that the .wait() method doesn't take any real effect beyond delaying the time the service comes up to an available state. Is there a defined reason to delay here?
Greetings,
My server at our home runs uWSGI, and I really wanted to have the app run and be managed uniformly with the rest of our apps. So I created a new daemon to run with uWSG with the added feature of taking flags from the environment. Tear down and restart are a little not so good, but I believe that is due to additional threading being managed by the Sickbeard daemon thread. The time it takes to tear down and start up a new version just hits a timeout and gets destroyed. All in all, running on my own uWSGI emperor managed server, config and save all seem to work.