Ready to get started with WordPress VIP? Contact us
Showing page 9 of 17
The WordPress.org open source community is comprised of talented individuals around the world. This community is always interested in receiving additional help from new contributors. Developers who support enterprise sites on the VIP Platform can lend a unique voice to WordPress that helps improve the project for all.
Enterprise Search will automatically index all public post statuses.
Enabling GitHub’s required status checks for branch protection ensures that no pull requests are merged unless they are free of issues, automatically detected by the VIP Code Analysis Bot (the Bot). This enforces a workflow where pull requests require developers to get clearance from the VIP Code Analysis Bot before they can merge the code.
Runtime Logs provides an aggregated, near real-time view into recent application logs generated by WordPress and Node.js environments on the WPVIP Platform. These logs provide insights into the current health of an environment and can be helpful for debugging issues.
How to serve static content on a Node.js environment.
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 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.
The IP Restrictions panel in the VIP Dashboard allows IP addresses—or ranges of IP addresses (aka subnets)—to be added to an “IP Allow List” or an “IP Deny List” for an application’s environment.
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.
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.