Ready to get started with WordPress VIP? Contact us
Showing page 18 of 26
By default, if enqueued, an application’s JavaScript and CSS files are concatenated in order to reduce the number of requests that occur on a single page load. CSS files are minified as well as concatenated, which reduces file size by removing unnecessary white space.
At a minimum, VIP customers have a production environment and can add additional “child” environments such as preprod and develop for testing and development purposes. New child environments can be requested by submitting a VIP Support ticket.
Node.js applications on WPVIP are provisioned with load-balanced pods with an optional Redis add-on. The WPVIP Platform is designed to run Node.js web applications—including decoupled/headless frontends to WordPress, microservices, REST APIs, GraphQL APIs, and middleware.
The WordPress VIP Platform has container-based infrastructure that allows customers to run WordPress applications and Node.js applications on Automattic’s world-class hardware and network infrastructure. VIP looks after hourly platform backups and 24/7 monitoring for all applications.
A reverse proxy is a server that sits between the end-user requesting information from a site and the VIP application serving the content. VIP only recommends using a proxy if it is absolutely necessary due to application or policy requirements.
Users granted access to an organization’s VIP Dashboard are assigned one of three Org roles (in order of most privileges to least): admin, member, and guest.
The /vip-config directory contains a file named vip-config.php.
Issues reported as VIP warnings should not be pushed to a production server unless a specific use case requires it. Some common issues reported as VIP warnings are listed below.
PHP_CodeSniffer (PHPCS) scans that are run against WordPress application code by the VIP Code Analysis Bot—or scans that are run manually after following the instructions to install PHPCS for WordPress VIP—will run with identical standards that include the WordPress-VIP-Go standard.
When considering non-production environments (e.g., develop, preprod) and their relationship to production environments, think of the code separately from the content, moving through environments in opposite directions.