gunicorn

Finally I migrated my development env from runserver to gunicorn/nginx. It'd be convenient to replicate the autoreload feature of runserver to gunicorn, so the server automatically restarts when source changes. Otherwise I have to restart the server manually with kill -HUP . Any way to avoid the manual restart? Dmitry Ziolkovskiy While this is old question, just for consistency - since version 19.0 gunicorn has --reload option. So no third party tools needed more. One option would be to use the --max-requests to limit each spawned process to serving only one request by adding --max-requests 1

I'm running django on gunicorn+nginx. I'm facing a problem with file uploads. Actually uploads are working fine but gunicorn times out thus causing this in nginx: 2011/07/25 12:13:47 [error] 15169#0: *2317 upstream timed out (110: Connection timed out) while reading response header from upstream, client: IP-ADDRESS, server: SERVER, request: "GET /photos/events/event/25 HTTP/1.1", upstream: "http://127.0.0.1:29000/photos/events/event/25", host: "HOST", referrer: "REFERER_ADDRESS" If I refresh the page, I can see all the photos are uploaded just fine. The problem is that it causes a timeout thus

python web 部署 web开发中，各种语言争奇斗艳，web的部署方面，却没有太多的方式。简单而已，大概都是 nginx 做前端代理，中间 webservice 调用程序脚本。大概方式： nginx + webservice + script nginx 不用多说，一个高性能的web服务器。通常用来在前端做反向代理服务器。所谓正向与反向（reverse），只是英文说法翻译。代理服务，简而言之，一个请求经过代理服务器从局域网发出，然后到达互联网上服务器，这个过程的代理为正向代理。如果一个请求，从互联网过来，先进入代理服务器，再由代理服务器转发给局域网的目标服务器，这个时候，代理服务器为反向代理（相对正向而言）。 正向代理：{ 客户端 ---》 代理服务器 } ---》 服务器 反向代理：客户端 ---》 { 代理服务器 ---》 服务器 } {} 表示局域网 nginx既可以做正向，也可以做反向。 webservice 的方式同样也有很多方式。常见的有 FastCGI ， WSGI 等。我们采用 gunicorn 为 wsgi容器。python为服务器script，采用 flask 框架。同时采用supervisor管理服务器进程。也就是最终的部署方式为： nginx + gunicorn + flask ++ supervisor 创建一个项目 mkdir myproject

I'm building an app with Flask, but I don't know much about WSGI and it's HTTP base, Werkzeug. When I start serving a Flask application with gunicorn and 4 worker processes, does this mean that I can handle 4 concurrent requests? I do mean concurrent requests, and not requests per second or anything else. When running the development server you get running app.run() , you get a single synchronous process, which means at most 1 requests being processed at a time. By sticking Gunicorn in front of it in its default configuration and simply increasing the number of --workers , what you get is