@westonruter @jonathanbardo In situations where wp is defined by an alias or addition to PATH in a .bash_profile, have you found a way to load this?

/usr/bin/env wp ?
I haven't tested yet. 😄

@danielbachhuber That's a valid scenario and I don't think we ever faced that problematic while we developed wp-cli-ssh.

Hm, not quite:

local ➜  wp-cli git:(2754-ssh) ✗ wp --ssh=hb
/usr/bin/env: wp: No such file or directory

That's a valid scenario and I don't think we ever faced that problematic while we developed wp-cli-ssh.

Unfortunately, it's a problem with the first server I tested with :(

Ah it looks difficult.

• Place the ~/.ssh/environment into local machine.
• Add PermitUserEnvironment yes in /etc/ssh/sshd_config on remote server.

http://stackoverflow.com/questions/216202/why-does-an-ssh-remote-command-get-fewer-environment-variables-then-when-run-man

@danielbachhuber This is why there was recent support for a wpcli_command config to handle situations where wp isn't on the PATH: xwp/wp-cli-ssh#27

This is why there was recent support for a wpcli_command config to handle situations where wp isn't on the PATH: xwp/wp-cli-ssh#27

@westonruter Did you explore trying to get the data out of .bash_profile ? I'd prefer to not have to institute a workaround...

No, I didn't. Also, perhaps the PHAR isn't even aliased as wp on the target environment. I think that there will ultimately need to be a way to provide an alternate path.

No, I didn't. Also, perhaps the PHAR isn't even aliased as wp on the target environment. I think that there will ultimately need to be a way to provide an alternate path.

I ended up creating a WP_CLI_PRE_SSH_CMD env variable, to offer a bit more flexibility:

WP_CLI::add_hook( 'before_ssh', function() {
    if ( $ssh = WP_CLI::get_runner()->config['ssh'] ) {
        list( $host, $path ) = explode( ':', $ssh );
        switch( $host ) {
            case 'hb':
                putenv( 'WP_CLI_SSH_PRE_CMD=export PATH=$HOME/bin:$PATH' );
                break;
        }
    }
});