Ready to get started with WordPress VIP? Contact us
Showing page 2 of 26
WordPress VIP supports PHP sessions for storing short-lived, ephemeral session data. Session data is backed by Memcached to improve performance, but to ensure a site’s stability and scalability the performance of its underlying code should be optimized wherever possible.
Direct access to an environment’s database is limited, but users can view data in a read-only phpMyAdmin console session or interact with the databases on WPVIP through WP-CLI commands run via VIP-CLI.
Enterprise Search can improve the performance of search results for a WordPress site, but limitations exist and default behaviors should be reviewed.
Redirects cannot be configured for any URLs that include /wp-content/uploads/*. The VIP File System, which resides upstream from application code, serves all files at that path. A reverse proxy is a possible solution for making a static asset available at a specific URL.
The default behavior of domains that are added to the "Domains & TLS" panel of an environment's VIP Dashboard is dependent on whether the www variant or the non-www variant is added.
Clearing the entire object cache or page cache for a site can negatively effect the site’s performance, particularly during a high traffic event. For this reason, when a code deployment occurs only a select group of cache clearing events will occur:
To successfully work with the VIP Local Development Environment, some dependencies must be installed and maintained on the user’s local machine.
Though the VIP Local Development Environment is designed to be as identical to a VIP Platform environment as possible, some features are not yet available in the local environment.
Similar to VIP Platform environments, the VIP Local Development Environment has container-based services. Some service containers may expose ports on the local machine.
Locations of WordPress VIP’s network of edge cache servers span the globe to efficiently store and serve content closest to an end user.