VIP File System

On the VIP Platform, media files that are uploaded to a WordPress site are not stored on the web container’s filesystem. Instead, an API is used to store the uploaded files in a separate read-only service called the VIP File System. This enables the WordPress application to automatically horizontally scale more efficiently across multiple hosts.

The VIP File System is a globally distributed object store that is seamlessly integrated into WordPress applications on VIP. The VIP File System provides high performance access to media files associated with a WordPress site. When browsers request these files, they are served through a dedicated system using the same domain as the site, with a long time to live (TTL).

• All common operations including uploads, cropping, editing, and deletes work as expected through the WordPress Admin dashboard.
• The File System provides dynamic image resizing and image transformation.
• Separate files are not created for intermediate images. Instead, the intermediate size of an image is dynamically generated at the time of a request.
• Media files can be imported to the File System with VIP-CLI, and media files for a site or an environment can be exported from the VIP Dashboard.
• Media files that are uploaded to a WordPress production environment are automatically shared with its associated non-production environments. When a data sync from a production environment to a non-production environment is completed, the target environment will automatically load the shared media files.
• By default, media files are cached by the Varnish page cache with a 1 year time to live (TTL). Cached content for media files can be purged by resource URL in the VIP Dashboard or with the VIP-CLI command vip cache purge-url.