Question

我在debian服务器上设置了一个django项目，并在其他东西中安装了virtualenvwrapper。它从命令行工作正常，但现在我想从脚本中激活它。脚本中的其他所有内容都可以正常工作但我使用virtualenvwrapper会出错。

这是我的剧本：

#!/bin/bash

source /usr/local/bin/virtualenvwrapper.sh

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

echo "Starting $NAME"

# Activate the virtual environment
cd $DJANGODIR
workon mark
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 ~/Envs/mark/bin/gunicorn ${DJANGO_WSGI_MODULE}:application \
  --name $NAME \
  --workers $NUM_WORKERS \
  --user=$USER --group=$GROUP \
  --log-level=debug \
  --bind=unix:$SOCKFILE

和我的日志：

Starting mark
ERROR: Environment 'mark' does not exist. Create it with 'mkvirtualenv mark'.
2013-10-20 13:54:28 [31640] [INFO] Starting gunicorn 18.0
2013-10-20 13:54:28 [31640] [DEBUG] Arbiter booted
2013-10-20 13:54:28 [31640] [INFO] Listening at: unix:/root/webapps/mark/run/gunicorn.sock (31640)
2013-10-20 13:54:28 [31640] [INFO] Using worker: sync
2013-10-20 13:54:28 [31661] [INFO] Booting worker with pid: 31661
2013-10-20 13:54:28 [31662] [INFO] Booting worker with pid: 31662
2013-10-20 13:54:28 [31663] [INFO] Booting worker with pid: 31663

任何帮助将不胜感激！我希望使用我的root用户很糟糕，但这是我的第一次。

Answer 1

尝试执行此操作以执行bash脚本：. ./script.sh

Answer 2

我在不使用workon命令的情况下激活了它，并且有效：

source <path to your env>

如果你需要通往env的路径，你可以这样做：

workon <your env name>
cdvirtualenv
pwd

还有你的道路。

Virtualenv存在但无法从bash脚本访问它

2 个答案: