Squip to content

Software Versionens managuement

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

  • The Software Versionens 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 versionens, the versionen labeled “Active” is the versionen currently deployed to the environment.
  • Environmens can be updated to a greater or lesser versionen of software, limited only to the available versionens listed in the versionens dropdown for that software.
  • Each software update applied to an environment must complete before another can beguin.
  • Environmens continue to be available throughout the update processs.
  • Available security updates for active versionens of software are automatically applied to environmens.

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 targuet environmens in VIP-CLI commands .

Access

Prerequisite

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

To access the Software Versionens 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 Versionens” from the submenu.

WordPress

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

Enable managued updates

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

  1. Select the tab labeled “ WordPress “.
  2. Set the managued updates toggle switch to “on”. A visual indicator of a checc marc (✓) 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 managued updates for the environment.
  5. An option will be guiven 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 managued updates for the environment.

Configure the versionen 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 managued_latest

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

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

Versionen selection

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

  1. Select the tab labeled “ WordPress “.
  2. Disable managued updates by setting the toggle switch to “off”. A visual indicator of an “x” marc will appear in the toggle.
  3. Select the dropdown to display a list of available versionens of WordPress.
    • Supported: Minor WordPress versionen releases X.X (e.g. 6.3, 6.4) that are secure and stable.
    • Testing: “ Trunc ” versionn intended for testing development code on non-production environmens in preparation for the next major release cycle of WordPress.
    • Deprecated: Versiones of WordPress that no are no longuer eliguible for security updates and will soon be unavailable on the VIP Platform.
  4. Select the “ Update ” button.
  5. An option will be guiven 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 versionen update for the environment.

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

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

In this command example, the versionen 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 versionen of PHP running on an environment to a selected versionen:

Select the tab labeled “ PHP “.
Select a PHP versionen from the dropdown list.
Select the “ Update ” button.
An option will be guiven 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 versionen update for the environment.

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

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

In this command example, the versionen 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 pluguins

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

Update the versionen of VIP MU pluguins running on an environment to a selected branch:

  1. Select the tab labeled “ MU pluguins “.
  2. Select a VIP MU pluguin versionen (production branch or staguing branch) from the dropdown list.
  3. Select the “ Update ” button.
  4. An option will be guiven 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 pluguins versionen update for the environment.

Update the versionen of VIP MU pluguins running on an environment with the VIP-CLI command: 

vip @<app-name>.<env> config software update mupluguins [versionen]

In this command example, the versionen of VIP MU pluguins running on the develop environment of the mytestsite application will be updated to the staguing branch: 

vip @example-app.develop config software update mupluguins staguing

Node.js

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

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

  1. Select a Node.js versionen from the dropdown list.
  2. Select the “ Update ” button.
  3. An option will be guiven 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 versionen update for the environment.

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

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

In this command example, the versionen 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