非默认静态位置的Flask Nginx和静态文件问题

Question

我正在使用nginx（通过gunicorn）为flask应用提供静态文件。

默认静态文件夹中的静态文件可以正常工作：

<link rel="stylesheet" href="{{ url_for('static', filename='css/fa/font-awesome.min.css') }}" />

但是对于我想限制登录用户访问权限的其他静态文件，我使用的是Flask提供的静态文件夹：

app.register_blueprint(application_view)

application_view = Blueprint('application_view', __name__, static_folder='application_static')

在HTML中，我这样调用一个静态文件：

<link rel="stylesheet" href="{{ url_for('application_view.static', filename='css/main.css') }}" />

然后在application / application_static中，我有受限制的静态文件。这在本地Flask安装上运行良好，但是当我使用Nginx从/ static文件夹提供文件的方式部署到生产计算机时，出现“网络错误：404未找到-website.com/application_static/main.css”。

关于如何配置Ngix来处理此问题的任何想法？

conf.d / mysitename.conf文件：

upstream app_server_wsgiapp {
     server localhost:8000 fail_timeout=0;
}

server {
 listen 80;
 server_name www.mysitename.com;
 rewrite ^(.*) https://$server_name$1 permanent;
}


server {
  server_name           www.mysitename.com;
  listen                443 ssl;
  #other ssl config here
  access_log            /var/log/nginx/www.mysitename.com.access.log;
  error_log             /var/log/nginx/www.mysitename.com.error.log info;
  keepalive_timeout     5;
  # nginx serve up static files and never send to the WSGI server
  location /static {
    autoindex on;
    alias /pathtositeonserver/static;
  }

  location / {
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
       proxy_set_header Host $http_host;
       proxy_redirect off;
       if (!-f $request_filename) {
         proxy_pass http://app_server_wsgiapp;
         break;
    }
  }

  # this section allows Nginx to reverse proxy for websockets
  location /socket.io {
    proxy_pass http://app_server_wsgiapp/socket.io;
    proxy_redirect off;
    proxy_buffering off;

    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "Upgrade";
  }
}

nginx.conf：

user www-data;
worker_processes 4;
pid /run/nginx.pid;

events {
        worker_connections 768;
        # multi_accept on;
}

http {
    sendfile on;
    tcp_nopush on;
    tcp_nodelay on;
    keepalive_timeout 65;
    types_hash_max_size 2048;

    include /etc/nginx/mime.types;
    default_type application/octet-stream;

    access_log /var/log/nginx/access.log;
    error_log /var/log/nginx/error.log;

    include /etc/nginx/conf.d/*.conf;
    include /etc/nginx/sites-enabled/*;
}

Answer 1

gunicorn除非您重新加载配置文件，否则旧代码仍将运行。

您可以停止并重新启动gunicorn，或者向gunicorn 进程发送HUP 信号。