Ready to get started with WordPress VIP? Contact us
Showing page 4 of 17
The Network Sites launch tool in the VIP Dashboard can be used to not only launch a site, but to update the Site Address (URL) of a network site to a new custom domain, subdomain, or custom domain with a subdirectory structure.
The VIP Platform is built to support a “code moves up; content moves down” workflow. This means that any new content needs to be added to the production site and then synced down to non-production environments. New code should be tested on the non-production environment prior to introducing it to the production environment.
After a custom TLS certificate has been provisioned, it is possible to switch to a Let’s Encrypt TLS certificate at any time.
To install a custom TLS certificate for a domain with a CSR that was not generated by VIP, customers must have in their possession a complete certificate chain generated by a Certificate Authority (CA).
A certificate signing request (CSR) from VIP can be generated in order to obtain a custom certificate from a Certificate Authority (CA). A CSR generated by VIP contains the necessary information, plus VIP’s authorization, that the CA needs to process a TLS certificate.
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 for a WordPress and Node.js environment.
The default path structure for URLs of files uploaded to a site’s WordPress Media Library is /wp-content/uploads/YYYY/MM/. An uploaded file will have a URL structure similar to: https://example.com/wp-content/uploads/2023/09/file.jpg
Files 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. Redirects cannot be configured for any URLs that include /wp-content/uploads/*.
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.