Ready to get started with WordPress VIP? Contact us
Showing page 25 of 26
On most platforms, media files uploaded to a WordPress site are stored in a filesystem local to the site’s web server. On the VIP Platform, media files uploaded or imported to a WordPress environment are stored on the VIP File System, which is an external object store. A WordPress site’s /wp-content/uploads/ directory is mapped to this external object store. This design provides better security and allows VIP’s CDN to more easily scale access to a site’s media.
VIP’s cron infrastructure leverages WP-Cron provided by WordPress Core, and cron jobs are initiated and regulated by Automattic’s Cron Control plugin. VIP’s Cron Control provides an optimized SQL table for WordPress Cron events. This approach satisfies the highly concurrent querying commonly seen on VIP sites. Each named event in the queue is handled in parallel with other events, allowing for a large event handling capacity. The VIP cron system orchestrates the activity of the event workers in the different containers, to avoid conflicts with two workers processing the same event.
New Relic is an application performance monitoring (APM) tool used to monitor the code and browser performance for WordPress environments or for Node.js environments.
The VIP Dashboard is a portal for application management, and for users to interact with the WordPress and Node.js VIP Platform environments that belong to those applications.
The behavior of the page cache does not vary for most cookies. For sites that personalize content based on a cookie that is not listed below, the response will be cached and served to the next user regardless of whether they have that cookie with the same value or not.
Custom configurations can be added to vip-config.php to handle redirects for secondary domains to the domain currently assigned to a WordPress site.
VIP helper functions for broader redirects:
An installed TLS certificate is required for a site to be launched on the VIP Platform. Because every site uses a custom domain for both the front-end and back-end admin area, TLS is a requirement to ensure that each site has a secure admin area and login process.
Modifying a hosts file allows a site to be tested with a new custom domain before the domain’s DNS has been pointed to VIP, or until the global DNS system has been updated for a domain. Modifying a hosts file only affects a user’s local computer, and will need to be repeated on any other devices that are used for testing.
New environments on the VIP Platform are provisioned with a convenience domain. The convenience domain is a subdomain of either .go-vip.net or .go-vip.co (e.g. example.go-vip.net).