Download a partial database backup
Download one or more specific tables from a database backup copy of a WordPress single site or a WordPress multisite environment.
Tag: how-to
Showing page 6 of 17
Download a full database backup
Download a backup copy of the entire database of a WordPress single site or a WordPress multisite environment.
Enable HTTPS for a VIP Local Development Environment
By default, VIP Local Development Environment URLs resolve with HTTP rather than HTTPS, the secure browsing protocol. When developing locally, some users may have a need for URLs to resolve at HTTPS (e.g. applications with payment integrations). For HTTPS to work as expected, a trusted digital certificate issued by a certificate authority (CA certificate) for the local environment must be added to the user’s machine.
Cache-control headers
The cache-control HTTP header provides an instructional value for controlling the caching of requests and responses in an end-user’s browser.
Flush the object cache
The object cache can be flushed with the WP-CLI command wp cache flush. WP-CLI commands must be run with VIP-CLI.
Enable HTTP request Log Shipping
When enabled, HTTP Request Log Shipping ships copies of an application’s HTTP request logs at 5-minute intervals to a customer’s Amazon Web Services (AWS) S3 buckets.
Database Backup Shipping
VIP's Database Backup Shipping feature makes it possible to ship database backups at regular intervals to an AWS S3 bucket managed by an organization.
Advanced usage
The VIP Local Development Environment is built to be as identical to a VIP Platform environment as possible, and designed to allow for a wide variety of options needed in local development. Once a user gains familiarity with dev-env commands and options, more advanced techniques and customizations can be explored when working with a local environment.
Enabling and disabling wp-parsely
The wp-parsely plugin is made available to all WordPress sites on the VIP Platform by VIP MU plugins.
Indexing user meta
By default, the users indexable feature is not activated. Once the users indexable feature is activated, all non-protected user meta is indexed.