Networking
The VIP Local Development Environment is composed of several Docker containers. Some of these containers bind host ports to be accessible from outside of their internal network.
Tag: tech-ref
Showing page 14 of 26
Basic usage
VIP Local Development Environment commands, options, and basic usage.
Audit Log
The Audit Log panel in the VIP Dashboard provides visibility into what is happening in an organization or an application. An audit trail of all management actions on the platform allows compliance with internal and external regulatory standards, and provides insight for debugging, security, and incident investigation.
Auto approvals
Several determinants are used by the VIP Code Analysis Bot to calculate whether a pull request can be automatically approved. Automatic approvals are executed without the use of any utilities, with the exception of the SVG analysis.
GitHub build status
During analysis by the VIP Code Analysis Bot, the GitHub interface will display a build status showing that analysis is In progress:
Bot feedback and messages
Feedback from the VIP Code Analysis Bot will be posted on reviewed pull requests based on the results of the automated scans including Vulnerability and Update Scan, PHPCS analysis, PHP linting, and SVG analysis. Feedback from the VIP Code Analysis Bot can be handled in several ways:
VIP Code Analysis Bot
For WordPress applications, the VIP Code Analysis Bot (“the Bot”) automatically analyzes code in pull requests made to any branch of a wpcomvip GitHub repository. The Bot helps to maintain the quality of the code submitted and to ensure the security and stability of the WordPress sites hosted on the VIP Platform.
Order of launching sites on a multisite
The “main site” of a network on a WordPress multisite environment is typically the first site (ID 1), and will be listed first in the Network Admin Sites screen.
Unlaunched
On VIP, an environment is considered unlaunched when
Launched
On VIP, an environment is considered launched when