Ready to get started with WordPress VIP? Contact us
Showing page 9 of 19
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 specifies directives that control how browsers, CDNs, and proxies handle cached responses. In most cases, the cache-control header value for WordPress and Node.js applications can be set to custom response directives.
The object cache can be flushed with the WP-CLI command wp cache flush. WP-CLI commands must be run with VIP-CLI.
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.
A VIP Local Development Environment can be configured to run with a local git clone of an application's wpcomvip GitHub repository.