Target environments with VIP-CLI commands
A VIP-CLI command can only be run against one environment at a time. Both an application and an environment type must be specified in a VIP-CLI command.
Tag: how-to
Showing page 11 of 18
Basic Authentication
Basic Authentication restricts site access to a limited set of users that have valid Basic Authentication login credentials
IP Restrictions
The IP Restrictions panel in the VIP Dashboard allows IP addresses to be added to an "IP Allow List" or an "IP Deny List" for an application's environment.
Point DNS for a domain to VIP
Once a site is ready to launch, the DNS for a site's new domain must be updated with the DNS provider and pointed at VIP for the site to be publicly available at that domain.
Save command output to a file
When running long-running custom WP-CLI commands, or commands that will affect many records, it is recommended to save the output to a file for review.
Choose what to index
By default, Enterprise Search will index all public post types, their statuses and their public taxonomy terms. Use allow lists and indexables to selectively index additional post types, statuses, taxonomies, and post meta.
Manage environment variables
Environment variables are a method for injecting information into WordPress and Node.js WPVIP Platform environments.
Check the index health
Use VIP-CLI to check if an index is in sync with a database, or to debug issues related to Enterprise Search.
Best practices for writing WP-CLI commands
By following best practices when writing a custom WP-CLI command, the command is more likely to be performant, and easier to debug and maintain over time.
Write custom WP-CLI commands at scale
On the VIP Platform, WP-CLI commands run in a container that is separate from a site’s web application, but it shares the Memcached and database containers. It is very important to set protections in place to prevent custom WP-CLI commands from inadvertently affecting a site’s performance.