Ready to get started with WordPress VIP? Contact Us
Showing page 7 of 26
A GitHub repository within the wpcomvip GitHub organization is created for every application and a branch is configured to deploy code to each of its environments. By default, application code is developed in an application’s provided wpcomvip GitHub repository and deployed via the Default Deployment method.
Each of an application’s VIP Platform environments can track its own specific branch of the application’s wpcomvip GitHub repository.
Drop-ins are files designed to replace, add, or enhance specific WordPress Core features.
Many different types of logs are available for WordPress and Node.js applications on the VIP Platform. Logs are a useful reference for debugging, hardening security, and incident investigation.
The WordPress VIP Platform provides a resilient infrastructure that includes full page cache, object cache, database indexes, database read replicas, separate handling of static files, dynamic image size transformation, and autoscaling of web containers.
Penetration tests, security assessments, or other scans can be run by a customer against their application's WordPress VIP Platform environments.
The version of PHP currently running on an environment can be referenced:
Check the status of a currently running import with the VIP-CLI command vip import sql status command.
Database structure for a WordPress multisite differs from the database structure of WordPress single site. In order to import a database to a VIP WordPress multisite network, the database file for import must be exported from a WordPress multisite.
A user’s ability to view or access Database Backup files in the VIP Dashboard or with VIP-CLI are defined by the Org role and permissions assigned to them by their organization.