Rollbacks in the VIP Dashboard
As an alternative to reverting a pull request in GitHub, a rollback to the image of a previous deployment can be performed in the Deployments panel of the VIP Dashboard.
Ready to get started with WordPress VIP? Contact us
Showing page 7 of 19
As an alternative to reverting a pull request in GitHub, a rollback to the image of a previous deployment can be performed in the Deployments panel of the VIP Dashboard.
All of the contents of a WordPress site's /wp-content/uploads/ directory are mapped to the VIP File System.
Files that are stored on the VIP File System can be overwritten programmatically or with VIP-CLI. Overwriting a file is useful for eliminating the need to set a redirect to a newer version of the file.
Before a PHP version is updated on a WordPress VIP Platform environment, all PHP files in an application’s GitHub repository should be scanned with PHPCS for potential incompatibility issues, and the identified issues should be resolved.
PHP linting identifies code syntax problems present in a repository’s PHP files.
Before a PHP version is updated on a WordPress VIP Platform environment, all PHP files in an application’s GitHub repository should be scanned for potential incompatibility issues, and the identified issues should be resolved.
When preparing for a PHP version update, creating automated tests can be useful for identifying incompatibilities with the updated version of PHP.
After application code has been scanned locally for an updated version of PHP, and identified incompatibilities have been fixed, test the performance of the updated code on a WordPress VIP Platform environment.
Install PHPCS at the project level so that PHPCS is available only when working within that project directory.
Install PHPCS globally so that PHPCS is available from anywhere on the local machine.