Updating CVEDIA-RT

Important

In versions before 2023.3.0, all created or edited instances were housed within the solution folders. However, as of version 2023.3.0, a change has been made to differentiate between "demo" instances and user instances. "Demo" instances remain within the solution folders, while user instances have been relocated to the instances folder.

For those looking to update their old instances to version 2023.3.0, you'll need to manually move them to the instances folder. Additionally, it's necessary to incorporate the solution ID within the JSON file of each instance. You can do this by adding the Solution property:

{
    "Solution": "Here goes the Solution ID",
    ...
}

To locate the solution ID, look for the SolutionId property in the base_config.json files in the solutions folder.

Windows users

On Windows there's no installation process, all you need to do is extract the zip file.

Previously changed solutions and instances may not work, so we recommend extracting to a new folder and copying your instances to files/instances/, and your custom solutions to files/solutions/.

Linux users

There are 2 ways to update on Linux:

1. Using the update.sh script

This script is designed to update both the container deployments and the redist bundle. It can update running instances with minimal downtime. This script will work in any Linux docker environment.

Run ./update.sh --help to see the update options.

2. Manually

Alternatively, you can simply download the new redist package and extract it to an empty folder.

If you have custom solutions, you can place them in the solutions/ folder within this new folder. Due LUA API changes old solutions may not work.

You will have to move also your instances to the instances/ folder.

Calling ./run.sh to execute CVEDIA-RT will not affect other existing installs.

Cloud users

If you have CVEDIA-RT deployed in a cloud environment with containers, you need to pull the latest docker image and trigger a rolling update.

If you have custom solutions and instances, we recommend doing the update in a staging area first to avoid downtime.