Port over aliases and SSH

Author: danielbachhuber

_posts/2016-07-29-version-0.24.0.md

@@ -29,26 +29,53 @@ Use `wp cli update` to install v0.24.0, representing [NNN resolved issues and pu
 
 ### Aliases and SSH support
 
+#### Effortlessly use WP-CLI against any WordPress install
 
-[#2755](https://github.com/wp-cli/wp-cli/pull/2755)
-
-[#2974](https://github.com/wp-cli/wp-cli/pull/2974)
-
-https://github.com/wp-cli/wp-cli/pull/3012
-https://github.com/wp-cli/wp-cli/pull/3013
-https://github.com/wp-cli/wp-cli/pull/3014
-https://github.com/wp-cli/wp-cli/pull/3016
-https://github.com/wp-cli/wp-cli/pull/3026
-https://github.com/wp-cli/wp-cli/pull/3040
-https://github.com/wp-cli/wp-cli/pull/3070
-https://github.com/wp-cli/wp-cli/pull/3093
-https://github.com/wp-cli/wp-cli/pull/3100
-https://github.com/wp-cli/wp-cli/pull/3117
-https://github.com/wp-cli/wp-cli/pull/3134
-https://github.com/wp-cli/wp-cli/pull/3135
-https://github.com/wp-cli/wp-cli/pull/3145
-https://github.com/wp-cli/wp-cli/pull/3161
-https://github.com/wp-cli/wp-cli/pull/3180
+WP-CLI aliases are shortcuts you register in your `wp-cli.yml` or `config.yml` to effortlessly run commands against any WordPress install.
+
+For instance, if I'm working locally on the runcommand theme, have registered a new rewrite rule, and need to flush rewrites inside my Vagrant-based virtual machine, I can run:
+
+    $ wp @dev rewrite flush
+    Success: Rewrite rules flushed.
+
+Then, once the code goes to production, I can run:
+
+    $ wp @prod rewrite flush
+    Success: Rewrite rules flushed.
+
+Look ma! No more SSH'ing into machines, changing directories, and generally spending a full minute to get to a given WordPress install.
+
+Additionally, alias groups let you register groups of aliases. If I want to run a command against both runcommand WordPress instances, I can use `@both`:
+
+    $ wp @both core check-update
+    Success: WordPress is at the latest version.
+    Success: WordPress is at the latest version.
+
+Aliases can be registered in your project's `wp-cli.yml` file, or your user's global `~/.wp-cli/config.yml` file:
+
+    @prod:
+      ssh: runcommand@runcommand.io~/webapps/production
+    @dev:
+      ssh: vagrant@192.168.50.10/srv/www/runcommand.dev
+    @both:
+      - @prod
+      - @dev
+
+#### But wait, what's the 'ssh' in there?
+
+WP-CLI now natively supports a `--ssh=<host>` global parameter for running a command against a remote WordPress install. Many thanks to XWP and their community for paving the way with [WP-CLI SSH](https://github.com/xwp/wp-cli-ssh).
+
+Under the hood, WP-CLI proxies commands to the `ssh` executable, which then passes them to WP-CLI installed on the remote machine. Your syntax for `-ssh=<host>` can be any of the following:
+
+* Just the host (e.g. `wp --ssh=runcommand.io`), which means the user will be inferred from your current system user, and the path will be the SSH user's home directory.
+* The user and the host (e.g. `wp --ssh=runcommand@runcommand.io`).
+* The user, the host, and the path to the WordPress install (e.g. `wp --ssh=runcommand@runcommand.io~/webapps/production`). The path comes immediately after the TLD of the host.
+
+Or, if you use a `~/.ssh/config`, `<host>` can be any host alias stored in the SSH config (e.g. `wp --ssh=rc` for me).
+
+Note you do need a copy of WP-CLI on the remote server, accessible as `wp`. Futhermore, `--ssh=<host>` won't load your `.bash_profile` if you have a shell alias defined, or are extending the `$PATH` environment variable. If this affects you, [here's a more thorough explanation](https://runcommand.io/to/wp-ssh-custom-path/) of how you can make `wp` accessible.
+
+Relevant pull requests include: [#2755](https://github.com/wp-cli/wp-cli/pull/2755), [#2974](https://github.com/wp-cli/wp-cli/pull/2974), [#3012](https://github.com/wp-cli/wp-cli/pull/3012), [#3013](https://github.com/wp-cli/wp-cli/pull/3013), [#3014](https://github.com/wp-cli/wp-cli/pull/3014), [#3016](https://github.com/wp-cli/wp-cli/pull/3016), [#3026](https://github.com/wp-cli/wp-cli/pull/3026), [#3040](https://github.com/wp-cli/wp-cli/pull/3040), [#3070](https://github.com/wp-cli/wp-cli/pull/3070), [#3093](https://github.com/wp-cli/wp-cli/pull/3093), [#3100](https://github.com/wp-cli/wp-cli/pull/3100), [#3117](https://github.com/wp-cli/wp-cli/pull/3117), [#3134](https://github.com/wp-cli/wp-cli/pull/3134), [#3135](https://github.com/wp-cli/wp-cli/pull/3135), [#3145](https://github.com/wp-cli/wp-cli/pull/3145), [#3161](https://github.com/wp-cli/wp-cli/pull/3161), [#3180](https://github.com/wp-cli/wp-cli/pull/3180).
 
 ### Future of WP-CLI