Skip to content

Software Versions management

The versions of software that are deployed to a WordPress or a Node.js VIP Platform environment can be managed in the VIP Dashboard or with the VIP-CLI command:
vip config software update <wordpress|php|nodejs|muplugins> <version> [options].

  • The Software Versions panel is environment-specific (e.g., Production, Develop). A different environment can be selected from the dropdown located at the upper left of the VIP Dashboard application view.
  • In the dropdown lists of software versions, the version labeled “Active” is the version currently deployed to the environment.
  • Environments can be updated to a greater or lesser version of software, limited only to the available versions listed in the versions dropdown for that software.
  • Each software update applied to an environment must complete before another can begin.
  • Environments continue to be available throughout the update process.
  • Available security updates for active versions of software are automatically applied to environments.

VIP-CLI command examples

For demonstration purposes, the <app-name> value example-app and the <env> value develop are used in the VIP-CLI command examples below. Read more about how to target environments in VIP-CLI commands.

Access

Prerequisite

To access the Software Versions panel, a user must have at minimum an Org member role or an App write role for that application.

To access the Software Versions panel:

  1. Navigate to the VIP Dashboard for an application.
  2. Select an environment from the environment dropdown located at the upper left of the VIP Dashboard.
  3. Select “Code” from the sidebar navigation at the left of the screen.
  4. Select “Software Versions” from the submenu.

WordPress

Select a version of WordPress to deploy to an environment, or enable managed updates that will automatically update WordPress to the latest stable version. Available minor releases and security releases for the active version of WordPress are automatically applied to environments.

Enable managed updates

Enabling managed updates for an environment will automatically update the environment’s version of WordPress to the latest stable release according to VIP’s platform release schedule. If managed updates are enabled for an environment that is not yet running the latest stable release version of WordPress, the environment will also be updated to the latest stable release version.

  1. Select the tab labeled “WordPress“.
  2. Set the managed updates toggle switch to “on”. A visual indicator of a check mark (✓) will appear in the toggle.
  3. Select the “Update” button.
  4. A dialog box will appear, prompting the user to confirm or cancel the update to the environment’s settings. Select the “Confirm” button to proceed with enabling managed updates for the environment.
  5. An option will be given in a dialog box to proceed with the update to the environment’s settings or to cancel the request. Select the “Update environment” button to proceed with enabling managed updates for the environment.

Configure the version of WordPress running on an environment to be automatically updated by the VIP Platform with the VIP-CLI command:

vip @<app-name>.<env> config software update wordpress managed_latest

In this command example, the version of WordPress on the develop environment of the mytestsite application will be set to managed:

vip @example-app.develop config software update wordpress managed_latest

Version selection

Update the version of WordPress running on an environment to a selected version:

  1. Select the tab labeled “WordPress“.
  2. Disable managed updates by setting the toggle switch to “off”. A visual indicator of an “x” mark will appear in the toggle.
  3. Select the dropdown to display a list of available versions of WordPress.
    • Supported: Minor WordPress version releases X.X (e.g. 6.3, 6.4) that are secure and stable.
    • Testing: “Trunk” version intended for testing development code on non-production environments in preparation for the next major release cycle of WordPress.
    • Deprecated: Versions of WordPress that no are no longer eligible for security updates and will soon be unavailable on the VIP Platform.
  4. Select the “Update” button.
  5. An option will be given in a dialog box to proceed with the update to the environment’s settings or to cancel the request. Select the “Update environment” button to proceed with the WordPress version update for the environment.

Update the version of WordPress running on an environment with the VIP-CLI command:

vip @<app-name>.<env> config software update wordpress [version]

In this command example, the version of WordPress running on the develop environment of the mytestsite application will be updated to 6.3:

vip @example-app.develop config software update wordpress 6.3

PHP

Update the version of PHP running on an environment to a selected version:

Select the tab labeled “PHP“.
Select a PHP version from the dropdown list.
Select the “Update” button.
An option will be given in a dialog box to proceed with the update to the environment’s settings or to cancel the request. Select the “Update environment” button to proceed with the PHP version update for the environment.

Update the version of PHP running on an environment with the VIP-CLI command:

vip @<app-name>.<env> config software update php [version]

In this command example, the version of PHP running on the develop environment of the mytestsite application will be updated to 8.2:

vip @example-app.develop config software update php 8.2

VIP MU plugins

The VIP Platform’s Must Use (“MU”) plugins are deployed to all VIP Platform WordPress applications. The VIP MU plugins production branch is intended for production environments, and the staging branch is useful for testing upcoming features on non-production environments.

Update the version of VIP MU plugins running on an environment to a selected branch:

  1. Select the tab labeled “MU plugins“.
  2. Select a VIP MU plugin version (production branch or staging branch) from the dropdown list.
  3. Select the “Update” button.
  4. An option will be given in a dialog box to proceed with the update to the environment’s settings or to cancel the request. Select the “Update environment” button to proceed with the VIP MU plugins version update for the environment.

Update the version of VIP MU plugins running on an environment with the VIP-CLI command:

vip @<app-name>.<env> config software update muplugins [version]

In this command example, the version of VIP MU plugins running on the develop environment of the mytestsite application will be updated to the staging branch:

vip @example-app.develop config software update muplugins staging

Node.js

Node.js Long Term Support (LTS) releases in Active or Maintenance status—as well as the next Active LTS candidate—are available for Node.js environments.

Update the version of Node.js running on an environment to a selected version:

  1. Select a Node.js version from the dropdown list.
  2. Select the “Update” button.
  3. An option will be given in a dialog box to proceed with the update to the environment’s settings or to cancel the request. Select the “Update environment” button to proceed with the Node.js version update for the environment.

Update the version of Node.js running on an environment with the VIP-CLI command:

vip @<app-name>.<env> config software update nodejs [version]

In this command example, the version of Node.js running on the develop environment of the mytestsite application will be updated to 22.0:

vip @example-app.develop config software update nodejs 22.0

Last updated: November 07, 2024

Relevant to

  • Node.js
  • WordPress