gunicorn | 易学教程

python web部署

阅读更多关于 python web部署

nginx + gunicorn + flask + supervisor的搭建为什么要加nginx。 Nginx能更好地直接处理静态资源（通过一些http request header），而把动态资源转发给后端服务器 Nginx也可以缓存一些动态内容 Nginx可以进行多台机器的负载均衡 Nginx可以更方便的实施一些安全策略。gunicorn 直接暴露还是蛮危险的，nginx挡一层，过滤掉一些恶意IP，同样的gunicorn处理起来就比较麻烦了。 nginx常见的两种代理方式：正向代理：{ 客户端 ---》代理服务器 } ---》服务器反向代理：客户端 ---》 { 代理服务器 ---》服务器 } {} 表示局域网 gunicorn： flask自带的app.run()服务，稳定性等各方面都不足，只适用于测试环境，线上环境还是要有专门的服务器，gunicorn和uWsgi就是常用的两个解决方案。 guincorn是支持wsgi协议的http server，gevent只是它支持的模式之一，是为了解决django、flask这些web框架自带wsgi server性能低下的问题。 supervisor： Linux的后台进程运行有好几种方法，例如nohup，screen等，但是，如果是一个服务程序，要可靠地在后台运行，我们就需要把它做成daemon

Can't reach Django default app via Gunicorn on AWS EC2 instance

阅读更多关于 Can't reach Django default app via Gunicorn on AWS EC2 instance

问题 I've been struggling with this problem for two days without success. I've created an instance of the default Django (1.6.1) app called "testdj", installed it on an Amazon AWS EC2 t1.micro instance running Ubuntu Server 13.10, and I'm trying to reach the default Django "It worked!" page via Gunicorn (v. 18). When I start gunicorn from the command line: gunicorn testdj.wsgi:application --bind [ec2-public-dns]:8001 I can see the page when I enter this URL: http://[ec2-public-dns]:8001 However,

Run startup code in the parent with Django and Gunicorn

阅读更多关于 Run startup code in the parent with Django and Gunicorn

问题 I need my code run at Django application startup, before Django starts listening for incoming connections. Running my code upon the first HTTP request is not good enough. When I use Gunicorn, my code must run in the parent process, before it forks. https://stackoverflow.com/a/2781488/97248 doesn't seem to work in Django 1.4.2: it doesn't run the Middleware's __init__ method until the first request is received. Ditto for adding code to urls.py . A quick Google search didn't reveal anything

Deploying Django with gunicorn No module named ImportError: No module named validation

阅读更多关于 Deploying Django with gunicorn No module named ImportError: No module named validation

问题 I m trying to deploy my Django project with using nginx, gunicorn and virtualenv. But i m getting following error while run this comment sudo gunicorn_django --bind test.com:8001 Log : Traceback (most recent call last): File "/opt/postjust/lib/python2.7/site-packages/gunicorn/arbiter.py", line 503, in spawn_worker worker.init_process() File "/opt/postjust/lib/python2.7/site-packages/gunicorn/workers/base.py", line 116, in init_process self.wsgi = self.app.wsgi() File "/opt/postjust/lib

Flask and gunicorn, multiple modules: circular imports - not all routes accessible

阅读更多关于 Flask and gunicorn, multiple modules: circular imports - not all routes accessible

问题 My problem is similar to Flask and Gunicorn on Heroku import error and Procfile gunicorn custom module name but I can't seem to fix it using their solutions. My Flask app has the following structure: appname/ run.py Procfile venv/ ... appname/ app.py views.py run.py: from appname import app app.run(debug=True) app.py: from flask import Flask app = Flask(__name__) @app.route('/') def home(): return "here" Procfile: web: gunicorn --pythonpath appname app:app views.py: from appname import app

serving flask app using gunicorn + nginx showing 404 [ec2]

阅读更多关于 serving flask app using gunicorn + nginx showing 404 [ec2]

问题 I am trying to serve a simple API by following this digitalocean tutorial. For testing I was earlier serving the API through gunicorn by doing a $ gunicorn --bind 0.0.0.0:5000 trumporate.wsgi:app And curling the API endpoint works inside the ec2 box $ curl -X GET http://0.0.0.0:5000/api/v1/trump/rant/ { "foo": "bar" } Now I shifted this gunicorn process to run at startup by making a systemd service # /etc/systemd/system/trumporate.service [Unit] Description=Gunicorn instance for trumporate

gunicorn ERROR (abnormal termination)

阅读更多关于 gunicorn ERROR (abnormal termination)

问题 im running a fabric script that, amongst other things, is supposed to restart gunicorn on an ubuntu server, the command is below: supervisorctl status projectname:gunicorn | sed "s/.*[pid ]$[0-9]\+$\,.*/\1/" | xargs kill -HUP the problem is, is that gunicorn doesnt appear to be running in the first place so the process cannot be killed, ive ssh'd into the amazon ec2 instance and ran sudo supervisorctl restart projectname:gunicorn' and I get an error response that says: projectname:gunicorn:

Django+gunicorn+nginx upload large file 502 error

阅读更多关于 Django+gunicorn+nginx upload large file 502 error

问题 Problem Uploading 1-2mb files works fine. When I attempt to upload 16mb file, i get 502 error after several seconds More detalied: I click "Upload" Google Chrome uploads file (upload status is changing from 0% to 100% in left bottom corner) Status changes to "Waiting for HOST", where HOST is my site hostname After a half of minute server returns "502 Bad Gateway" My view: def upload(request): if request.method == 'POST': f = File(data=request.FILES['file']) f.save() return redirect(reverse

Why does Gunicorn use port 8000/8001 instead of 80?

阅读更多关于 Why does Gunicorn use port 8000/8001 instead of 80?

问题 I busy setting up a development environment for Django Framework using Gunicorn (as Django service) and NGINX (as a Reverse Proxy). When I look at several tutorials like this one and this one, I see that they use port 8000 and port 8001 ( http://127.0.0.1:8000 and http://127.0.0.1:8001 ). Is there a special reason not to use port 80, like any other webserver? Port 8000 is often used for radio streaming and malware, so why? BTW: I am running it using Virtualenv on a Ubuntu 12.04 system. 回答1:

Django exceeds maximum Postgres connections

阅读更多关于 Django exceeds maximum Postgres connections

问题 I am experiencing a problem with a Django application that is exceeding the maximum number of simultaneous connections (100) to Postgres when running through Gunicorn with async eventlet workers. When the connection limit it reached the application starts returning 500 -errors until new connections can be established. This is my database configuration: DATABASES = { 'default': { 'ENGINE': 'django.contrib.gis.db.backends.postgis', 'NAME': 'django', 'USER': 'django', 'HOST': 'postgres', 'PORT':