With version 5.8.0 translate5 is able to run completely in docker containers - making installation and scaling much more easier.
Therefore all services were migrated into docker containers or already existing docker containers are used.
An existing translate5 installation may remain as it is, only users of the non public VisualReview Plug-In has to setup and configure the following needed services as docker containers as explained below.
In other words: if you setup translate5 completely with docker containers the steps in this manual here is not needed!
Since the VisualReview Plug-In is not public, the pdfconverter container is also not public. In order to use it, we have to provide you an access token to docker hub. Please ask for that! See also translate5 docker installation manual for additional information.
The translate5 docker installation manual contains a docker-compose configuration file for all services and more advanced information.
Docker containers and local DNS configuration
The IP address of visualbrowser must be updated in /etc/hosts after a renew/restart of the visualbrowser container!
This is an open todo to make it static: https://stackoverflow.com/questions/27937185/assign-static-ip-to-docker-container
The following code block must be added to the apache vhost section serving translate5 - replace ABSOLUTE_PATH_TO_TRANSLATE5 with your local translate5 directory path:
Restart apache after that.
The following configurations contains the URLs pointing to the services in the docker containers. They are set correctly by default if you add the above entries to /etc/hosts.
The old "runtimeOptions.plugins.VisualReview.shellCommandGoogleChrome" is removed in favour of the above URL based configuration.