Django:Digital Ocean Django image gunicorn未使用python venv
我已经缩小了这个问题的范围,我不知道如何解决它 Gunicorn没有在venv中运行 Gunicorn脚本位于/etc/init/Gunicorn.confDjango:Digital Ocean Django image gunicorn未使用python venv,python,django,Python,Django,我已经缩小了这个问题的范围,我不知道如何解决它 Gunicorn没有在venv中运行 Gunicorn脚本位于/etc/init/Gunicorn.conf description "Gunicorn daemon for Django project" start on (local-filesystems and net-device-up IFACE=eth0) stop on runlevel [!12345] # If the process quits unexpectadly
description "Gunicorn daemon for Django project"
start on (local-filesystems and net-device-up IFACE=eth0)
stop on runlevel [!12345]
# If the process quits unexpectadly trigger a respawn
respawn
setuid django
setgid django
chdir /home/django
exec gunicorn \
--name=project \
--pythonpath=project \
--bind=0.0.0.0:9000 \
--config /etc/gunicorn.d/gunicorn.py \
project.wsgi:application
然后这里是该文件中的gunicorn.py文件引用
"""gunicorn WSGI server configuration."""
from multiprocessing import cpu_count
from os import environ
def max_workers():
return cpu_count() * 2 + 1
max_requests = 1000
worker_class = 'gevent'
workers = max_workers()
errorlog = '/var/log/gunicorn/error.log'
accesslog = '/var/log/gunicorn/access.log'
我不知道从这里到哪里去…结果是将exec行更改为
exec path/to/venv/bin/gunicorn
已经足够激活venv了,但是有一些依赖项需要安装,日志文件权限需要正确,我通过访问/var/log/upstart/gunicorn.log发现了一切,结果是将exec行更改为
exec path/to/venv/bin/gunicorn
足够激活venv了,但是有一些依赖项需要安装,日志文件权限需要正确,我通过访问/var/log/upstart/gunicorn.log发现了一切