-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Document non-gunicorn based approaches for deployment #1120
Comments
what are the advantages/drawbacks of both approach as I think it's good to know why there's an alternative ? I already made for tornado a deployment like you described , nginx with a upstream configured to round-robin accross different processes handled by supervisor so if that's what you looking for, I can create a PR :) |
You are getting rid of intermediate (gunicorn) but should control/monitor your services by external tool ( I very appreciate a contribution into this part of doc. |
I see I think I need to read a bit more about how gunicorn is working, because I always thought it was only for traditionnal sync framework and that it would not play well with asyncio ones (or at least it will hurt 'peformances' by inducing extra buffering etc. ) |
Gunicorn does hurt performance but overhead is relative low. |
+1 this would be awsome. Since I was having problems with gunicorn #1223, I tried to run aiohttp web.run_app behind nginx without gunicorn, but couldn't get things to work. Tried just proxy_pass to the 127.0.0.1 port but no go. I'm not sure what i was doing wrong. nginx isn't that easy to understand and the interactions between webservers is really tricky. |
Search does not work for
I'm not sure why, but the 'Gunicorn' result leads to I was unable to find the mistake in |
Fixed by aiohttp==1.1.1 |
The text was updated successfully, but these errors were encountered: