VIP-CLI command reference
Available VIP-CLI commands and their options can be reviewed by running vip --help
(or -h
).
Ready to get started with WordPress VIP? Contact us
Showing page 4 of 26
Available VIP-CLI commands and their options can be reviewed by running vip --help
(or -h
).
Many performance issues can be identified with available performance analysis tools. Once these performance issues are identified, developers should work towards correcting them.
If added, the maintenance.php
drop-in will be ignored by a VIP Platform WordPress environment. The Automattic-authored “Maintenance Mode” plugin is the suggested alternative for the functionality that the maintenance.php
drop-in provides.
WordPress VIP does not maintain a list of “approved” plugins. Plugins of the customer’s choice can be installed to extend a site’s functionality.
The Insights & Metrics panel, located in the application view of the VIP Dashboard, provides insights into the performance, health, and usage of an application.
Code that is committed to the deploying branch of a WordPress environment should contain all needed assets. On deploy, no additional building is done except for submodule includes. When using composer, for example, code should be committed to a branch only after running composer install
. An alternative to this is to set up a continuous integration and deployment (CI/CD) method.
Code deployments typically take up to 5 minutes to complete. The amount of time required to complete a code deployment can vary depending on:
By default, the post_status
of a query is set to publish
for anonymous users on the front end. It is not set in any WP_ADMIN context, including Ajax queries.
For most issues that occur when attempting to log in to the VIP Dashboard an informative error message will be returned. The error message will indicates a possible underlying cause for the issue.
Single Sign-On (SSO) for logging in to the VIP Dashboard can be configured for an organization as an optional—or enforced—authentication method.