Update - Relution
Introduction
Follow these steps to upgrade your Relution installation.
Docker installation
Edit the docker-compose.yml
file and replaceimage: relution/relution:xxx
with image: relution/relution:latest
.
Updating Relution is then very easy:
cd /opt/relution/
docker compose pull
docker compose up --detach
Make sure to compare docker_relution
with the name of the Relution container container_name
that you specified in the docker-compose.yml
if it is different from the default.
This command will download the latest version of the Docker image and install it. The Relution service will be unavailable for a few minutes while the container is restarting.
The following command can be used to delete old containers and caches, which can free up a lot of memory.
docker system prune -a
WARNING! This will remove:
- all stopped containers
- all networks not used by at least one container
- all images without at least one container associated to them
- all build cache
Are you sure you want to continue? [y/N]
Native installation Linux
- download the latest relution package: Latest Relution Package → .
- stop the Relution service.
- Backup your Relution database.
- backup the installation directory.
mv <INSTALL_DIR> <INSTALL_DIR>.bak
- extract the zip package to
<INSTALL_DIR>
. - set the owner of the
<INSTALL_DIR>
directory, for example:sudo chown -R relution:relution /opt/relution
- copy
<INSTALL_DIR>.bak/application.yml
to<INSTALL_DIR>/application.yml
. - start the Relution service.
- wait until the Relution service is started.
Native Installation Windows
- download the latest Relution package: Latest Relution Package →
- stop the Relution service
services.msc
- save the existing installation directory to
relution_bak_
- extract the zip package to the old installation directory
<INSTALL_DIR>
- copy the configuration file from the backup
relution_bak_/application.yml
to<INSTALL_DIR>/application.yml
- start the Relution service
- wait until the Relution service has started. in the directory
<INSTALL_DIR>/log/relution.txt
the log can be viewed
The database is being updated to the latest version. Updating the database may take some time."
Known error messages
The service
Relution
onLocal Computer
could not be started. The service did not return an error. It may be an internal Windows error or an internal service error. Please contact your system administrator if the problem persists.
If you receive the following message when starting the Relution service, it could indicate that the Java version used is too low.
To fix this, please download and install the latest Java 17 LTS from the following link: Adoptium Java
During installation, activate the option Set Home PATH
, otherwise you will have to enter the Home PATH manually in the Windows variables afterwards.
After installation, restart the Relution service.
Checklist after the update.
- Do relution apps on mobile devices also need an update?
- Do custom CSS files need an update?
- Are enrolled devices still accessible?
- Send an
update device information
action to a device.
- Send an
- Is enrollment still working for the different platforms?
Update from version 4 to Relution 5
To be able to update to version 5.x, version 4.79.2 or a newer version of Relution 4.79 must be installed, because otherwise the database migration scripts will not work.
We recommend backing up the database before updating.
Update Docker to Relution Version 5
To update the Docker environment, edit the docker-compose.yml
file enter 4.79.2
at the image tag.
image: relution/relution:4.79.2
Start the Docker and let install the update to version 4.79.2. Then shut down the container again.
Change the image tag in the docker-compose.yml
file back to latest
.
image: relution/relution:latest
Update Native to Relution Version 5
First install version 4.79.2 → as described above.
After installing 4.79.2, you can install version 5 from the
Latest Relution Package → .