Import database files
Use VIP-CLI to import a full database file when migrating a site to the VIP Platform, or import a partial database file to update specific tables on a WordPress environment.
Ready to get started with WordPress VIP? Contact Us
Showing page 18 of 19
Use VIP-CLI to import a full database file when migrating a site to the VIP Platform, or import a partial database file to update specific tables on a WordPress environment.
Media can be imported to the VIP File System with VIP-CLI. This is especially useful for the process of migrating a WordPress site to the VIP Platform.
To set up a reverse proxy for a site on the VIP Platform, configurations must be made within the account of the reverse proxy provider, to the DNS of the site’s domain, in the VIP application’s codebase, within the site’s VIP Dashboard, and to the site itself. It is strongly recommended that the configurations of a reverse proxy are kept as simple as possible.
Retiring a WordPress single site or Node.js application involves retiring the VIP application. Retiring an individual network site on a WordPress multisite does not require retiring the VIP application. See the Application page for the definition of VIP application.
The VIP Platform’s VIP_GO_APP_ENVIRONMENT constant and the WordPress function wp_get_environment_type() can both be used to customize environment-specific behavior in code.
How to serve small amounts of static content on a WordPress environment.
The output of robots.txt can be modified with WordPress actions and filters.
A WordPress multisite network is a collection of sites that all share the same WordPress installation core files. They can also share plugins and themes. The individual sites in the network have separate directories for media uploads within the shared installation, and separate tables in the database.
Before shifting traffic to a new site make sure the site is working as expected and that it is as performant and secure as possible. In general, continuous performance checks should occur during development on a non-production environment, but tests on a production environment just before launch are also recommended.
Scanning code locally with PHP_CodeSniffer (PHPCS) provides useful feedback on code quality based on a defined set of coding standards.