Ready to get started with WordPress VIP? Contact us
Showing page 9 of 16
An application on VIP can include one or more environments, and users may have access to more than one application hosted on VIP. A VIP-CLI command can only be run against one environment at a time, so both an application and an environment type must be specified in a VIP-CLI command.
Basic Authentication is useful when a static list—or range—of IP addresses required by other methods of site restriction are not available. Common uses for Basic Authentication are for restricting access to non-production environments, or to production environments that are not yet launched and still under development.
Access to individual environments of an application can be restricted by specifying a list of IP addresses—or ranges of IP addresses (aka subnets)—in the VIP Dashboard’s IP Allow List. These settings are useful for sites with highly sensitive content, intranets, and non-production environments. Once an IP Allow List has been applied to an environment, any and all requests from an IP address outside of the allowed list or range will be denied.
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 WPVIP for the site to be publicly available at that domain.
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.
By default, Enterprise Search will not index every post type, taxonomy, or meta. Indexing unnecessary content can result in:
Environment variables are a method for injecting information into WordPress and Node.js WPVIP Platform environments.
There is a wide range of subcommands available in wp vip-search health to check if your index is in sync with the database and to assist in debugging.
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.
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.