Closed westonruter closed 10 years ago
@westonruter I think we have 2 solutions for this kind of scenario. One is to have a different alias, which might not be desirable (didn't we do this so it's mostly transparent to the user). Or do another exec
(we are too late in the process to send the other command back to local wp-cli) with the basic wp-cli command and removing the ssh argument altogether.
Please see PR, you can now have an alias and it will fallback if no config is provided in the yml file.
If I have my bash alias set up:
And I try to use WP-CLI on a WordPress install which is not configured for SSH, then I get an error:
If the SSH config is not present, then shoukd WP-CLI SSH should just silently ignore it was ever passed? Or is it just bad to have
wp
alias towp ssh
? Should instead the alias bewpvag
, for example?