blocks|key|1280115|text|我只是使用了一个简单的包装器函数virtualenv()，可以调用它而不是run()。它不使用cd上下文管理器，因此可以使用相对路径。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1280116|def+virtualenv(command):
++++"""
++++Run+a+command+in+the+virtualenv.+This+prefixes+the+command+with+the+source
++++command.
++++Usage:
++++++++virtualenv('pip+install+django')
++++"""
++++source+=+'source+%25(project_directory)s/bin/activate+&&+'+%25+env
++++run(source+%2B+command)|code-block|syntax|javascript|1280117|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I'm just using a simple wrapper function virtualenv() that can be called instead of run(). It doesn't use the cd context manager, so relative paths can be used.

<pre><code>def virtualenv(command):
 """
 Run a command in the virtualenv. This prefixes the command with the source
 command.
 Usage:
 virtualenv('pip install django')
 """
 source = 'source %(project_directory)s/bin/activate &amp;&amp; ' % env
 run(source + command)
</code></pre>

blocks|key|1494959|text|作为bitprophet预测的更新:使用Fabric+1.0，您可以使用prefix()和您自己的上下文管理器。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1494960|from+__future__+import+with_statement
from+fabric.api+import+*
from+contextlib+import+contextmanager+as+_contextmanager

env.hosts+=+['servername']
env.user+=+'deploy'
env.keyfile+=+['$HOME/.ssh/deploy_rsa']
env.directory+=+'/path/to/virtualenvs/project'
env.activate+=+'source+/path/to/virtualenvs/project/bin/activate'

@_contextmanager
def+virtualenv():
++++with+cd(env.directory):
++++++++with+prefix(env.activate):
++++++++++++yield

def+deploy():
++++with+virtualenv():
++++++++run('pip+freeze')|code-block|syntax|javascript|1494961|entityMap|0|LINK|mutability|MUTABLE|url|http://docs.fabfile.org/en/1.13/api/core/context_managers.html#fabric.context_managers.prefix^0|10|8|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

As an update to bitprophet's forecast: With Fabric 1.0 you can make use of <a href="http://docs.fabfile.org/en/1.13/api/core/context_managers.html#fabric.context_managers.prefix" rel="noreferrer">prefix()</a> and your own context managers.

<pre><code>from __future__ import with_statement
from fabric.api import *
from contextlib import contextmanager as _contextmanager

env.hosts = ['servername']
env.user = 'deploy'
env.keyfile = ['$HOME/.ssh/deploy_rsa']
env.directory = '/path/to/virtualenvs/project'
env.activate = 'source /path/to/virtualenvs/project/bin/activate'

@_contextmanager
def virtualenv():
 with cd(env.directory):
 with prefix(env.activate):
 yield

def deploy():
 with virtualenv():
 run('pip freeze')
</code></pre>

blocks|key|1280238|text|这是我在本地部署中使用virtualenv的方法。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1280239|使用fabric的path()上下文管理器，您可以使用来自virtualenv的二进制文件运行pip或python。|1280240|from+fabric.api+import+lcd,+local,+path

project_dir+=+'/www/my_project/sms/'
env_bin_dir+=+project_dir+%2B+'../env/bin/'

def+deploy():
++++with+lcd(project_dir):
++++++++local('git+pull+origin')
++++++++local('git+checkout+-f')
++++++++with+path(env_bin_dir,+behavior='prepend'):
++++++++++++local('pip+freeze')
++++++++++++local('pip+install+-r+requirements/staging.txt')
++++++++++++local('./manage.py+migrate')+#+Django+related

++++++++++++#+Note:+previous+line+is+the+same+as:
++++++++++++local('python+manage.py+migrate')

++++++++++++#+Using+next+line,+you+can+make+sure+that+python+
++++++++++++#+from+virtualenv+directory+is+used:
++++++++++++local('which+python')|code-block|syntax|javascript|1280241|entityMap|0|LINK|mutability|MUTABLE|url|http://docs.fabfile.org/en/1.7/api/core/context_managers.html?highlight=path#fabric.context_managers.path^0|B|A|0|1B|3|1F|6|9|6|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@$9|Y|A|Z|B|C]|$9|10|A|11|B|C]]|D|@$9|12|A|13|1|14]]|E|$]]|$1|H|3|I|5|J|7|15|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|16|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

This is my approach on using <code>virtualenv</code> with local deployments.

Using fabric's <a href="http://docs.fabfile.org/en/1.7/api/core/context_managers.html?highlight=path#fabric.context_managers.path">path()</a> context manager you can run <code>pip</code> or <code>python</code> with binaries from virtualenv.

<pre><code>from fabric.api import lcd, local, path

project_dir = '/www/my_project/sms/'
env_bin_dir = project_dir + '../env/bin/'

def deploy():
 with lcd(project_dir):
 local('git pull origin')
 local('git checkout -f')
 with path(env_bin_dir, behavior='prepend'):
 local('pip freeze')
 local('pip install -r requirements/staging.txt')
 local('./manage.py migrate') # Django related

 # Note: previous line is the same as:
 local('python manage.py migrate')

 # Using next line, you can make sure that python 
 # from virtualenv directory is used:
 local('which python')
</code></pre>

blocks|key|1495082|text|以下是一个装饰器的代码，它将导致在任何run/sudo调用中使用Virtual+Environment：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1495083|#+This+is+the+bash+code+to+update+the+$PATH+as+activate+does
UPDATE_PYTHON_PATH+=+r'PATH="{}:$PATH"'.format(VIRTUAL_ENV_BIN_DIR)

def+with_venv(func,+*args,+**kwargs):
++"Use+Virtual+Environment+for+the+command"

++def+wrapped(*args,+**kwargs):
++++with+prefix(UPDATE_PYTHON_PATH):
++++++return+func(*args,+**kwargs)

++wrapped.__name__+=+func.__name__
++wrapped.__doc__+=+func.__doc__
++return+wrapped|code-block|syntax|javascript|1495084|然后，要使用装饰器，请注意装饰器的顺序很重要：|1495085|@task
@with_venv
def+which_python():
++"Gets+which+python+is+being+used"
++run("which+python")|1495086|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Here is code for a decorator that will result in the use of Virtual Environment for any run/sudo calls:

<pre><code># This is the bash code to update the $PATH as activate does
UPDATE_PYTHON_PATH = r'PATH="{}:$PATH"'.format(VIRTUAL_ENV_BIN_DIR)

def with_venv(func, *args, **kwargs):
 "Use Virtual Environment for the command"

 def wrapped(*args, **kwargs):
 with prefix(UPDATE_PYTHON_PATH):
 return func(*args, **kwargs)

 wrapped.__name__ = func.__name__
 wrapped.__doc__ = func.__doc__
 return wrapped
</code></pre>

and then to use the decorator, note the order of the decorators is important:

<pre><code>@task
@with_venv
def which_python():
 "Gets which python is being used"
 run("which python")
</code></pre>

blocks|key|1495163|text|感谢所有张贴的答案，我想为此再添加一个替代方案。有一个模块fabric-virtualenv，它可以提供与代码相同的功能：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1495164|>>>+from+fabvenv+import+virtualenv
>>>+with+virtualenv('/home/me/venv/'):
...+++++run('python+foo')|code-block|syntax|javascript|1495165|fabric-virtualenv使用fabric.context_managers.prefix，这可能是一种很好的方式:)|style|CODE|1495166|entityMap|0|LINK|mutability|MUTABLE|url|https://pypi.python.org/pypi/fabric-virtualenv/^0|T|H|0|0|0|J|U|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|Z|8|@$A|10|B|11|K|L]]|9|@]|C|$]]|$1|M|3|-4|5|6|7|12|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]]]

Thanks to all answers posted and I would like to add one more alternative for this. There is an module, <a href="https://pypi.python.org/pypi/fabric-virtualenv/" rel="nofollow">fabric-virtualenv</a>, which can provide the function as the same code:

<pre><code>&gt;&gt;&gt; from fabvenv import virtualenv
&gt;&gt;&gt; with virtualenv('/home/me/venv/'):
... run('python foo')
</code></pre>

fabric-virtualenv makes use of <code>fabric.context_managers.prefix</code>, which might be a good way :)

blocks|key|1280463|text|如果你想将软件包安装到环境中，或者想要根据环境中的软件包运行命令，我找到了这个hack来解决我的问题，而不是编写复杂的fabric方法或安装新的操作系统软件包：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1280464|/path/to/virtualenv/bin/python+manage.py+migrate/runserver/makemigrations++#+for+running+commands+under+virtualenv

local("/home/user/env/bin/python+manage.py+migrate")++++#+fabric+command


/path/to/virtualenv/bin/pip+install+-r+requirements.txt+++#+installing/upgrading+virtualenv

local("/home/user/env/bin/pip+install+-r+requirements.txt")++#++fabric+command|code-block|syntax|javascript|1280465|这样，您可能不需要激活环境，但可以在该环境下执行命令。|1280466|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

If you want to install the packages to environment or want to run commands according to the packages you have in environment, I have found this hack to solve my problem, instead of writing complex methods of fabric or installing new OS packages:

<pre><code>/path/to/virtualenv/bin/python manage.py migrate/runserver/makemigrations # for running commands under virtualenv

local("/home/user/env/bin/python manage.py migrate") # fabric command


/path/to/virtualenv/bin/pip install -r requirements.txt # installing/upgrading virtualenv

local("/home/user/env/bin/pip install -r requirements.txt") # fabric command
</code></pre>

This way you might not need to activate the environment, but you can execute commands under the environment.

blocks|key|1495316|text|这个方法适用于我，你也可以应用这个方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1495317|from+fabric.api+import+run+
#+...+other+code...
def+install_pip_requirements():
++++run("/bin/bash+-l+-c+'source+venv/bin/activate'+"
++++++++"&&+pip+install+-r+requirements.txt+"
++++++++"&&+/bin/bash+-l+-c+'deactivate'")|code-block|syntax|javascript|1495318|假设venv是您的虚拟环境目录，并在适当的地方添加此方法。|offset|length|style|CODE|1495319|entityMap^0|0|0|2|4|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

This approach worked for me, you can apply this too.

<pre><code>from fabric.api import run 
# ... other code...
def install_pip_requirements():
 run("/bin/bash -l -c 'source venv/bin/activate' "
 "&amp;&amp; pip install -r requirements.txt "
 "&amp;&amp; /bin/bash -l -c 'deactivate'")
</code></pre>

Assuming <code>venv</code> is your virtual env directory and add this method wherever appropriate.

blocks|key|1495431|text|我使用pyenv和pyenv-virtualenvwrapper插件。我在workon上没有成功，而是使用了这个(fabric+2.5)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1495432|with+c.prefix('source+/home/mirek/.virtualenvs/%25s/bin/activate'+%25+PROJECT):
++++with+c.prefix('cd+/home/mirek/%25s/%25s'+%25+(PROJECT,+PROJECT)):
++++++++c.run('python+manage.py+....')|code-block|syntax|javascript|1495433|对于git+pull代理转发是很好的，即。在~/.ssh/config中使用ssh+-A+..或更好的语言，就像这样：|offset|length|style|CODE|1495434|Host+forpsi
++++HostName+xx.xx.xx.xx
++++IdentityFile+/home/mirek/.ssh/id_ed25519_xxx
++++ForwardAgent+yes|1495435|现在，在开发机器上，如果您在代理中有一个私钥(在ssh-add之后，或者如果您在创建git+push之后在~/.ssh/config中有AddKeysToAgent+yes+)，那么git+pull不应该询问密钥的密码。|1495436|entityMap^0|0|0|2|8|M|D|12|9|0|0|O|7|16|8|1H|D|1W|I|2J|8|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@$I|V|J|W|K|L]|$I|X|J|Y|K|L]|$I|Z|J|10|K|L]]|9|@]|A|$]]|$1|M|3|N|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|12|8|@$I|13|J|14|K|L]|$I|15|J|16|K|L]|$I|17|J|18|K|L]|$I|19|J|1A|K|L]|$I|1B|J|1C|K|L]]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|R|$]]

I use pyenv with plugin pyenv-virtualenvwrapper. I had no success with workon, instead I use this (fabric 2.5):
<pre><code>with c.prefix('source /home/mirek/.virtualenvs/%s/bin/activate' % PROJECT):
 with c.prefix('cd /home/mirek/%s/%s' % (PROJECT, PROJECT)):
 c.run('python manage.py ....')
</code></pre>
For <code>git pull</code> agent forwarding is good, ie. <code>ssh -A ..</code> or better in <code>~/.ssh/config</code> something like this:
<pre><code>Host forpsi
 HostName xx.xx.xx.xx
 IdentityFile /home/mirek/.ssh/id_ed25519_xxx
 ForwardAgent yes
</code></pre>
And now on the development machine if you have a private key in the agent (after <code>ssh-add</code> or if you have <code>AddKeysToAgent yes</code> in <code>~/.ssh/config</code> after you made <code>git push</code>) then <code>git pull</code> should not ask for the passphrase of the key.

I want to run my fabric script locally, which will in turn, log into my server, switch user to deploy, activate the projects .virtualenv, which will change dir to the project and issue a git pull.

<pre><code>def git_pull():
 sudo('su deploy')
 # here i need to switch to the virtualenv
 run('git pull')
</code></pre>

I typically use the workon command from virtualenvwrapper which sources the activate file and the postactivate file will put me in the project folder. In this case, it seems that because fabric runs from within shell, control is give over to fabric, so I can't use bash's source built-in to '$source ~/.virtualenv/myvenv/bin/activate'

Anybody have an example and explanation of how they have done this?

Activate a virtualenv via fabric as deploy user

服务器

Django

我想在本地运行fabric脚本，它将依次登录到我的服务器，切换用户到deploy，激活项目.virtualenv，这将更改项目的目录并发出git拉。def git_pull():    sudo('su deploy')    # here i need to switch to the virtualenv    r...

问作为部署用户通过fabric激活virtualenv
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问作为部署用户通过fabric激活virtualenvEN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问作为部署用户通过fabric激活virtualenv
EN