Upgrading from previous REVEN versions
Upgrading from REVEN<=2.7.1 to >=2.8.0
Please follow the dedicated guide, as this upgrade requires a Debian upgrade.
Upgrading from REVEN 2.x
To upgrade from a previous REVEN v2.x version, please follow the steps below.
For Docker packages
-
Stop the running REVEN Project Manager by calling the
run.sh
script from the directory of the REVEN 2.x installation being upgraded. -
Extract the new Docker package to a new directory.
-
If you previously modified the
run.sh
script in the existing installation, port these modifications to therun.sh
script in the new directory. -
Run
run.sh
from the new directory.
For Debian packages
-
Stop the running REVEN Project Manager by calling the
stop.sh
script from the directory of the REVEN 2.x installation being upgraded. -
Extract the archive to a new directory, as described in the Installation section.
-
Run
install.sh
as an administrator to update system dependencies. -
Upon running
start.sh
for the first time, you will be provided with the choice to migrate your scenarios from your existing REVEN 2.x installations. -
If upgrading from REVEN < 2.4, you will be prompted for your license key on the first start of the Project Manager. You should have received your license key by email. If not, please contact support.
For REVEN in a VM installations
Please follow instructions detailed in the installation page.
Upgrading from REVEN v1.x
To upgrade from a REVEN v1.x version, you will need to perform a fresh installation by following the installation instructions.