django, gunicorn, nginx下設定subpath
google上找到滿多都是apache和uwsgi的設定,
這個設定讓我花了好一段時間才找到。
設定是wsgi server和有用nginx的upstream才有用
很簡單只需要設定
以下是稍微詳細一點的nginx設定
這個設定讓我花了好一段時間才找到。
設定是wsgi server和有用nginx的upstream才有用
很簡單只需要設定
proxy_set_header SCRIPT_NAME $your_subpath
這樣django就會正常囉!
以下是稍微詳細一點的nginx設定
upstream some_urls {
# 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 unix:/path/to/your/gunicorn/socket fail_timeout=0;
}
server {
listen 80;
server_name example.com;
client_max_body_size 4G;
location /your_subpath/ {
# 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;
# setting for running in a subpath
proxy_set_header SCRIPT_NAME /your_subpath;
# 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://some_urls;
break;
}
}
Blogger貼code還真不好看就是了
參照PEP 333
對python而言SCRIPT_NAME是用來知道這個python程式他對server而言他是在哪個路徑下面。所以上面範例中的/your_subpath設定後就能用了
參照PEP 333
對python而言SCRIPT_NAME是用來知道這個python程式他對server而言他是在哪個路徑下面。所以上面範例中的/your_subpath設定後就能用了
留言
張貼留言