- This topic is empty.
-
AuthorPosts
-
August 11, 2024 at 5:35 pm #25941
Stephanie
Guestjust 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
August 11, 2024 at 5:36 pm #25942Mark
Guestmentioned here:
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).
August 11, 2024 at 5:37 pm #25943Olivia
Guestsimply add these @ flags to your
wpcommands to target the desired environment!August 11, 2024 at 5:39 pm #25944Sara
Guestexamples of this usage:
https://www.tech-otaku.com/web-development/using-wp-cli-to-update-wordpress-theme-options/
August 11, 2024 at 5:46 pm #25946Donald
GuestWhat if you don’t specify the @ environment in SlickStack for
wpcommands?August 12, 2024 at 7:05 am #25979Ruth
GuestI have used WP CLI for a while, and never knew you could do this lol
August 12, 2024 at 7:06 am #25980Kyle
GuestWhat if you don’t specify the @ environment in SlickStack
SlickStack default is:
path: /var/www/html url: https://@SITE_FULL_DOMAINin the
/var/www/meta/wp-cli.ymlconfig 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
August 15, 2024 at 3:48 am #26014Kevin
Guest💯
-
AuthorPosts