Update Relution
Follow these steps to update your Relution installation.
Due to changes in the database migration it is mandatory to update from version 2.7 to version 3.2 before updating to the latest version of Relution. |
From version 2.7 to 3.2
Docker
Edit the docker-compose.yml
and replace
image: {productSmall}/{productSmall}:2.7
with
image: {productSmall}/{productSmall}:3.2
Updating Relution is then as simple as:
cd /opt/relution/
docker-compose pull
docker-compose up --detach
Make sure to replace docker_relution with the name of the Relution container (“container_name”) you’ve specified in your docker-compose.yml if the name deviates from our template.
|
This will pull the docker image for Relution version 3.2 before restarting the containers. The Relution service will be unavailable for a minute or two until the containers have finished rebooting.
Linux
-
Download the Relution 3.2 ZIP archive.
-
Stop the Relution service
-
Ensure the service’s Java processes have terminated
-
Backup your Relution database
-
Uninstall the Relution service
-
run
<INSTALL_DIR>/bin/uninstall_init.sh
as root
-
-
Backup the installation directory
-
e.g.
mv <INSTALL_DIR> <INSTALL_DIR>.bak
-
-
Extract the ZIP archive to
<INSTALL_DIR>
-
Copy
<INSTALL_DIR>.bak/config-admin
to<INSTALL_DIR>/config-admin
-
Run
sudo java -jar setup.jar
and follow the on-screen instructions.-
We recommend to install Relution as a system service
-
Relution will detect if the system uses sysv-init or systemd
-
-
Wait for the Relution service to start
-
The database is be migrated to the latest version
-
The system configuration is moved to the database
-
Windows Server
-
Download the Relution 3.2 ZIP archive
-
Stop the Relution service
-
Ensure the service’s Java processes have terminated
-
Backup your Relution database
-
Uninstall the Relution service
-
run
<INSTALL_DIR>\bin\uninstall_service.bat
as Administrator
-
-
Backup the installation directory
-
e.g.
move <INSTALL_DIR> <INSTALL_DIR>.bak
-
-
Extract the ZIP archive to
<INSTALL_DIR>
-
Copy
<INSTALL_DIR>.bak\conf\*
into<INSTALL_DIR>\conf\
-
Do not copy the file
gofer.conf
-
-
Run
java -jar setup.jar
from an administrative shell and follow the on-screen instructions-
Do install Relution as a Windows service, this is the only way to start Relution on Windows
-
-
Wait for the Relution service to start
-
The database is be migrated to the latest version
-
The system configuration is moved to the database
-
From version 3.2 or newer to latest version
Docker
image: {productSmall}/{productSmall}:3.2
with
image: {productSmall}/{productSmall}:latest
Updating Relution is then as simple as:
cd /opt/relution/
docker-compose pull
docker-compose up --detach
Make sure to replace docker_relution with the name of the Relution container (“container_name”) you’ve specified in your docker-compose.yml if the name deviates from our template.
|
This will pull the latest docker image for each container before restarting the containers. The Relution service will be unavailable for a minute or two until the containers have finished rebooting.
Manual update
-
Download the latest Relution package
-
Stop the Relution service
-
Backup your Relution database
-
Backup the installation directory
-
e.g.
mv <INSTALL_DIR> <INSTALL_DIR>.bak
-
-
Extract the ZIP archive to
<INSTALL_DIR>
-
Copy
<INSTALL_DIR>.bak/conf/sql.conf
to<INSTALL_DIR>/conf/sql.conf
-
Start the Relution service
-
Wait for the Relution service to start
-
Configuration is migrated to
<INSTALL_DIR>/application.yml
-
The database is migrated to the latest version
-
From version 4.x to latest version
Docker
Edit the docker-compose.yml
file and replace
image: {productSmall}/{productSmall}:xxx
with
image: {productSmall}/{productSmall}:latest
Updating Relution is then as simple as:
cd /opt/relution/
docker-compose pull
docker-compose up --detach
Make sure to replace docker_relution with the name of the Relution container (“container_name”) you’ve specified in your docker-compose.yml if the name deviates from our template.
|
This will pull the latest docker image for each container before restarting the containers. The Relution service will be unavailable for a minute or two until the containers have finished rebooting.
Manual update
-
Download the latest Relution package
-
Stop the Relution service
-
Backup your Relution database
-
Backup the installation directory
-
e.g.
mv <INSTALL_DIR> <INSTALL_DIR>.bak
-
-
Extract the ZIP archive to
<INSTALL_DIR>
-
Copy
<INSTALL_DIR>.bak/application.yml
to<INSTALL_DIR>/application.yml
-
Start the Relution service
-
Wait for the Relution service to start
-
The database is migrated to the latest version
-