Ready to get started with WordPress VIP? Contact us
Showing page 7 of 17
A custom configuration file enables a VIP Local Development Environment with specific settings to be created in a repeatable manner. If the configuration file is committed to an application’s source-controlled GitHub repository, multiple team members with access to that repository can use the file to create VIP Local Development Environments with identical settings.
The cache-control HTTP header provides an instructional value for controlling the caching of requests and responses in an end-user’s browser.
The object cache can be flushed with the WP-CLI command wp cache flush. WP-CLI commands must be run with VIP-CLI.
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.
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.
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.
Parse.ly is provided by WordPress VIP as an Integration and can be activated on any WordPress site on the platform.
By default, the users indexable feature is not activated. Once the users indexable feature is activated, all non-protected user meta is indexed.
A Node.js site can be launched on its own or as part of a decoupled site launch.
Media files can be uploaded, imported, or proxied to a running VIP Local Development Environment. It is recommended to import media files after a VIP Local Development Environment is confirmed to be up and running and has been configured to run with locally cloned application code.