Managing Node.js versions
VIP supports all Node.js Long Term Support (LTS) releases in Active or Maintenance status—as well as the next Active LTS candidate—for Node.js environments.
Ready to get started with WordPress VIP? Contact us
Showing page 13 of 26
VIP supports all Node.js Long Term Support (LTS) releases in Active or Maintenance status—as well as the next Active LTS candidate—for Node.js environments.
All WordPress sites on the VIP Platform are provisioned with robust, built-in performance features such as:
Runtime Logs provides an aggregated, near real-time view into recent application logs generated by WordPress and Node.js environments on the WPVIP Platform.
The cached version of previously requested content is served by the edge server located closest to the user making the request. This provides low latency and very high site performance for a site's traffic.
Logins to the VIP Dashboard can be authenticated with a GitHub user account, a WordPress.com user account, or with an existing Single Sign-On (SSO) configuration. Once logged in, a user’s ability to access and interact with areas of the VIP Dashboard is defined by the Org role or App role that is assigned to the user.
Database Backups run automatically for all WordPress environments and can be viewed and downloaded in the application view of the VIP Dashboard and with VIP-CLI. Database backups are useful for internal security policies, to automate regular data ingestion for analysis systems, and can be imported to local development environments.
Understand the purpose of the /docs directory in your WordPress VIP application's codebase.
Pull requests with changes that affect more than 1000 lines of code can be overwhelming for a reviewer and slow down the review process. Reduce the complexity of code review by breaking a larger pull request into multiple, smaller pull requests.
A WordPress or Node.js VIP application is comprised of:
A .phpcs.xml.dist
file exists by default in all wpcomvip GitHub repositories that were created for WordPress applications since January 2022. The file contains a suggested configuration for PHP_CodeSniffer (PHPCS). When running PHPCS locally, this root configuration applies to all code within the application repository.