什么是gunicorn.sock?

use*_*060 10 unix sockets django nginx gunicorn

我是Michal Karzynski的gunicorn-django教程之后的新手.我在Ubuntu 14上使用Django 1.7.4,我对gunicorn脚本的设置如下

#!/bin/bash

NAME="mytestapp"                                  # Name of the application
DJANGODIR=/var/www/testapp/src             # Django project directory
SOCKFILE=/var/www/testapp/run/gunicorn.sock  # we will communicte using this unix socket
USER=ubuntu                                        # the user to run as
GROUP=ubuntu                                     # the group to run as
NUM_WORKERS=3                                     # how many worker processes should Gunicorn spawn
DJANGO_SETTINGS_MODULE=testapp.settings             # which settings file should Django use
DJANGO_WSGI_MODULE=testapp.wsgi                     # WSGI module name

echo "Starting $NAME as `whoami`"

# Activate the virtual environment
cd $DJANGODIR
export DJANGO_SETTINGS_MODULE=$DJANGO_SETTINGS_MODULE
export PYTHONPATH=$DJANGODIR:$PYTHONPATH

# Create the run directory if it doesn't exist
RUNDIR=$(dirname $SOCKFILE)
test -d $RUNDIR || mkdir -p $RUNDIR

# Start your Django Unicorn
# Programs meant to be run under supervisor should not daemonize themselves (do not use --daemon)
exec gunicorn ${DJANGO_WSGI_MODULE}:application \
  --name $NAME \
  --workers $NUM_WORKERS \
  --user=$USER --group=$GROUP \
  --bind=0.0.0.0:8000 \
  --log-level=debug \
  --log-file=-
Run Code Online (Sandbox Code Playgroud)

当我将绑定设置更改为unix:$ SOCKFILE时,我的脚本仍然运行但我无法连接到我的浏览器.在这个问题中,我已经读过在生产服务器上部署0.0.0.0:8000并不明智.

我对unix套接字有所了解,但我不知道如何使用unix套接字文件来为我的网站提供服务.我曾尝试以超级用户身份编辑套接字文件,但操作系统不允许我打开它.

如何设置套接字文件以允许我提供我的页面?

PS:这是我的nginx配置文件

upstream hello_app_server {
# fail_timeout=0 means we always retry an upstream even if it failed
# to return a good HTTP response (in case the Unicorn master nukes a
# single worker for timing out).

server 127.0.0.1:8000 fail_timeout=0;
} 

server {

    listen   80;
    server_name test.com;

    client_max_body_size 4G;

    access_log /var/www/testapp/src/logs/nginx-access.log;
    error_log /var/www/testapp/src/logs/nginx-error.log;

    location /static/ {
        alias   /var/www/testapp/src/static/static_dirs/;
    }

    location /media/ {
        alias   /var/www/testapp/src/static/media/;
    }

    location / {
        # an HTTP header important enough to have its own Wikipedia entry:
        #   http://en.wikipedia.org/wiki/X-Forwarded-For
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

        # enable this if and only if you use HTTPS, this helps Rack
        # set the proper protocol for doing redirects:
        # proxy_set_header X-Forwarded-Proto https;

        # pass the Host: header from the client right along so redirects
        # can be set properly within the Rack application
        proxy_set_header Host $http_host;

        # we don't want nginx trying to do something clever with
        # redirects, we set the Host: header above already.
        proxy_redirect off;

        # set "proxy_buffering off" *only* for Rainbows! when doing
        # Comet/long-poll stuff.  It's also safe to set if you're
        # using only serving fast clients with Unicorn + nginx.
        # Otherwise you _want_ nginx to buffer responses to slow
        # clients, really.
        # proxy_buffering off;

        # Try to serve static files from nginx, no point in making an
        # *application* server like Unicorn/Rainbows! serve static files.

        if (!-f $request_filename) {
            proxy_pass http://hello_app_server;
            break;
        }

    }

    # Error pages
    error_page 500 502 503 504 /500.html;
    location = /500.html {
        root /var/www/testapp/src/static/;
    }
}
Run Code Online (Sandbox Code Playgroud)

Dan*_*man 6

您应该使用像 nginx 这样的反向代理来坐在 gunicorn 前面,而这实际上是为您的站点提供服务的。它们通过套接字进行通信。

gunicorn 文档有一个示例 nginx 配置,它完全可以做到这一点,尽管显然您应该使 sockfile 与您在 gunicorn 配置中放置的内容相匹配。