wp-plugin-mass-operation

You can run WP-CLI plugin commands across multiple sites by generating a target set from your infra inventory, pulling SSH credentials from 1Password, and executing the appropriate WP-CLI command per site path. This ensures correct per-server user selection and post-operation validation.

Yes, bulk installing WordPress plugins on RunCloud sites is supported via SSH and WP-CLI. The process targets RunCloud webapps using the correct server user, such as zeus, runcloud, or runcloud2, along with the specific per-site paths for accurate deployment.

You deploy mu-plugins on AWS Bitnami sites using browser automation and the WP File Manager elFinder put flow. This method enforces strict base64 and MD5 integrity checks for deployed PHP payloads, followed by an enforced cleanup policy that deactivates and deletes the manager after use.

wp-plugin-mass-operation works with RunCloud API v3 to determine targets and inventory, but executes authenticated SSH-based deploy steps for plugin file writing where the API lacks direct file writing support.

Browser automation for plugin mass operations is limited to AWS Bitnami sites where SSH-based WP-CLI access is unavailable. It requires controlled browser interactions for file placement and outcome validation, making it less direct than SSH-based WP-CLI execution on RunCloud sites.

You need 1Password to retrieve credentials via the hermes_tools terminal for WordPress plugin mass operations. Strict credential handling is mandatory for authenticating SSH sessions across RunCloud sites and accessing AWS Bitnami targets.