On Thu, Jul 4, 2013 at 3:29 AM, Roger Barnes wrote:
> It looks like you may be missing a space after the word "source".
>
> My fabfile has these helpers, given an env.virtualenv and env.app_dir
> setting...
Another way to do it is to provide a shell script that sets up the
appropriate environment
It looks like you may be missing a space after the word "source".
My fabfile has these helpers, given an env.virtualenv and env.app_dir
setting...
def ve_run(command, func=run, base_dir=None, *args, **kwargs):
base_dir = base_dir or env.app_dirwith cd(base_dir):with
prefix("sou
I had a similar issue - running manage.py through Fabric simply didn't pan
out - even after following the Fabric documentation. Also tried the
--noinput switch with no luck? I do not have a ready answer right now, but
I do intend to look into this. I am sure it has (and is being) done plenty
times
I use Python Fabric to deploy. Works great for accessing the remote server,
install dependencies, run linux commands, etc..
But when I try to run *file commands manage.py Django*, NOT work!
Example of my fabfile.py:
with prefix ('source/home/user/env/bin/activate'):
with cd ('path/to/your/p
4 matches
Mail list logo
