Requires wp to load

[ryanshoover]

trafficstars

Right now this has to be run from a local WP install's directory (with a working WP site). That's because it uses wp_remote_post and WP_Http_Cookie. If we move this to just use a cURL, then we can get rid of the WP dependency.

At that point does it even need to be in wp-cli...?

[hello-jason]

The idea of splitting wpe into its own command makes a lot of sense here, as opposed to that always being an alias for WP-cli's wp command with wpe-specific arguments passed in.

I would like to see the wpe command perform WPE platform-specific functions by default (like trigger a backup), by specifying an install name as it currently works, then I would like to allow a flag, like -wpcli, which would take a WP-cli command after it and pass that WP-cli command off to the specified install.

[ryanshoover]

@hello-jason A workaround may be the alias mentioned in the readme. Leaving it as part of wp-cli lets us easily do things like #2 and a feature I'm currently working on - pull an install's DB into your local WP instance.

If we leave this tool with its current functionality, then no need to be tied to wp-cli. If we start looking at ways to interact between local WP sites and WPE WP sites, then it should be part of wp-cli.

Yeah, not sure on the best direction here yet.