Hi Nathan I just have two questions. 1. Is the drush binary inside the folder drush? PATH entries should point to a folder, not a binary. 2. Is there any reason you can't use the full path to the binary in your run() call? That would eliminate the need to set your PATH. On Mar 21, 2013 8:38 AM, "Nathan Kleekamp" <[email protected]> wrote:
> I'm trying to run a command installed in my home directory on a remote > server. It's in my $PATH on the remote server (via .bash_profile), but > Fabric isn't seeing it. I've tried adding it to my $PATH using Fabric's path > context > manager<http://docs.fabfile.org/en/1.6/api/core/context_managers.html#fabric.context_managers.path> > like > so: > > def test_path(): > with path('/path/to/sources/drush'): > run('echo $PATH') > run('drush') > > However, I'm getting: > Fatal error: run() received nonzero return code 127 while executing! > > Fabric is executing: > Executed: /bin/bash -l -c "export > PATH=\"\$PATH:\"/home/kleekampnf/sources/drush\" \" && drush" > > I think this is happening because the last dir in the path is being > interpreted by bash as "/path/to/source/drush " (trailing space) - an > invalid directory. I'm just wondering if this is a bug or a feature and I'm > doing it wrong. > > See my related Stackoverflow post: > http://stackoverflow.com/questions/15533841/setting-path-variable-with-fabric-1-6-0 > > Thanks, > Nathan > > _______________________________________________ > Fab-user mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/fab-user > >
_______________________________________________ Fab-user mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/fab-user
