Helmut4 Server

The purpose of this guide is to provide instructions for a successful deployment of the latest version of Helmut4.


The installation of Helmut4 on a host which follows the system requirements which are listed below is straight forward. As Helmut4 is running within a docker environment the installation of these components are required - if the host is in an restricted network it may be needed to install those in advance or allow temporary access to the accordingly repositories. By default all necessary applications are installed automatically by executing the bash install script:

  • docker-ce

  • docker-ce-cli

  • containerd.io

  • docker-compose

  • httpie

  • jq

Helmut4 is storage agnostic which means that the system needs at least one share to be used properly, but it can be used with multiple shares as well. Any share needs to be mounted on the linux host system as well as within specific docker containers. At least one storage should be mounted via fstab before starting the installation as this one is needed. To start the installation executed the following command as sudo:

Full installation (downloading all depenedcies) curl -s https://repo.moovit24.de/install/setup.sh | bash

By default the script will install the current Helmut4 version on the server, we recommend to update the version manually to the latest/same version after the installation.

Portainer / Helmut4-Docker configuration

After the successful installation of Helmut4 the volumes of the host machine need to be handed over to the Docker environment. To do so navigate to Portainer, which runs on port 9000:

Portainer web GUI http://ip-helmutserver:9000

The default user/password to log in is admin/admin Please consider to change this password as soon as possible!

Every drive that is to be added to the system must be mapped into the container. To do this, the drive must first be mounted at the operating system level. The drive mounted at the operating system level is now mapped into the Docker container in the following way:

Drive on operating system level: /mnt/helmut

Drive on Docker container level: /Volumes/helmut

Drive mapped between operation system level and Docker container: /mnt/helmut_1:/Volumes/helmut_1

This mnt to Volumes mapping is set up, to allow setting up easy workflows on Mac OS X, as every network share is mounted to /Volumes There are 5 different containers that always have to have access to specific volumes to run specific tasks. For example: If the server should create projects on a specific volume, this volume needs to be mapped into the FX Container, as this container is responsible for creating projects. To add volume to a container follow these steps:

  • click on “primary”

  • click on “stacks”

  • click on “helmut4”

  • click on the tab “Editor"

Add or change the volumes and click update the stack once finished with this task.

Example: adding share "testing" which is mapped on the host into /mnt/testing volumes:

- /etc/localtime:/etc/localtime:ro

- /mnt/helmut:/Volumes/helmut

- /mnt/testing:/Volumes/testing

Updating Helmut4

There are two update channels available for Helmut 4 - main & development An update can be accessed with sudo rights on the command line of the host

Main update channel | helmut-snapshot

Stable releases will be published every three months, the latest release can be found in the release notes. This version is covered by the support contract and the software maintenance agreement is valid for this version. Critical bugs will be fixed in stable release. Please consider checking the supported Adobe versions before updating

helmut-snapshot <snapshot version number>

eg helmut-snapshot 4.6.0

After executing the update command the Portainer password is required

Development update channel | helmut-update


The development channel is only for internal use and requires an additional password, this one can be requested by contacting support@moovit.de

Be aware that those builds are MAINLY UNTESTED and can cause problems!

Last updated