Ready to get started with WordPress VIP? Contact us
Showing page 9 of 17
Environments with Default Deployment enabled are configured to track a specific branch of an application’s wpcomvip GitHub repository. For example, new production environments are set up to track a branch named production by default. Pushing any changes to this branch (via a push, merge, or rebase) triggers an automatic deployment to the production environment.
Testing a reverse proxy‘s configurations should be done with a site’s convenience domain URL in preparation for a site launch. When the proxy testing is complete, and the site is ready to launch, the final production domain (e.g. https://www.example.com) should replace the convenience domain in the configurations.
Reverse proxy configurations should be tested extensively prior to a site launch.
PHP is continuously under development to improve performance and security with every released version. Though every version brings improvements, sometimes new requirements for code syntax or breaking changes are introduced as well.
Node.js applications on the VIP Platform must use npm to manage their dependencies. Other dependency managers such as yarn are not supported.
Database content can be imported or synced to a running VIP Local Development Environment. Before syncing or importing content, It is recommended to first confirm that the VIP Local Development Environment is up and running as expected. Configuring the environment to load locally cloned application code prior to adding data can also help prevent unexpected errors .
Enterprise Search can be optionally enabled for WordPress Admin dashboard queries using custom code and filters.
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.