[Stephanie]

just for better search visibility we are adding this thread… please note that SlickStack customizes WP-CLI to have the following environment flags:

@dev, @development, @staging, @prod, @production, @both, and @all

[Mark]

mentioned here:

Commands

By default, our WP-CLI implementation will target the production site. However, you can use the environment aliases @dev, @development, @staging, @prod, @production to target a specific SlickStack environment(s) if desired.

You can also use @both to target both staging and production, and @all to target all three of these environments (note that, you must first enable dev/staging sites in your ss-config).

[Olivia]

simply add these @ flags to your wp commands to target the desired environment!

[Sara]

examples of this usage:

https://www.tech-otaku.com/web-development/using-wp-cli-to-update-wordpress-theme-options/

[Donald]

What if you don’t specify the @ environment in SlickStack for wp commands?

[Ruth]

I have used WP CLI for a while, and never knew you could do this lol

[Kyle]

What if you don’t specify the @ environment in SlickStack

SlickStack default is:

path: /var/www/html
url: https://@SITE_FULL_DOMAIN

in the /var/www/meta/wp-cli.yml config file.

This means the production site will be targeted by default, and for Multisite, the main site will be targeted by default.

https://github.com/littlebizzy/slickstack/blob/master/modules/wordpress/wp-cli/wp-cli-yml.txt

[Kevin]

💯

[Author]

Posts