Applications and their environments

The VIP Platform supports WordPress single site, WordPress multisite, and Node.js applications.

“Application” collectively refers to a single GitHub repository codebase, the web server environment(s) to which the codebase deploys, and the database and media files associated with those environments.

Read more about applications

Every application has a production environment, and typically an application also has two non-production environments (e.g. preprod and develop). Non-production environments should be used for testing and developing code for new features, bug fixes, and testing version upgrades for software and plugins.

Read more about VIP Platform environments

Web containers for all environments run in read-only mode. VIP provides tooling—VIP Dashboard and VIP-CLI—for managing environments and their settings.

Software management for environments

Versions of software—like WordPress, PHP, and Node.js—that are running on an environment can be managed in the VIP Dashboard or with VIP-CLI. Only versions of software that are eligible for security updates will be available to choose from.

As updated versions of software are released, VIP will ensure that they are available for your team to select and begin upgrade testing as soon as possible. VIP will also automatically deploy any security patches for current software versions or other protections as they become available to mitigate critical vulnerabilities.

Read more about software management

Code moves up; content moves down

VIP’s infrastructure is built to support a “Code moves up; content moves down” development workflow for WordPress and Node.js applications.

Code moves upward (develop → production).

All new code should initially be deployed to non-production environments where development teams can perform tests and make adjustments as-needed. Developers should confirm that the code is error-free and working as expected before the code is moved upward and deployed to the production environment.

Content (database and media files) moves downward (production → develop).

Every WordPress environment has its own unique database instance. The database of the production environment is the authoritative source of content, storing the most current content changes. VIP’s tooling only allows databases to be synced from production downward to non-production environments. Moving content in one direction protects the production database from overwrites and data loss.

Read more about syncing data from production to non-production environments

Similarly, media files associated with an environment are stored in the VIP File System. The VIP File System has a built-in feature to automatically share the media files associated with a production environment with its non-production environments after a data sync. This simplifies the process to make a non-production environment nearly identical to production.

Read more about shared media files