With version 5.8.0 translate5 is able to run completely in docker containers - making installation and scaling much more easier.
Therefore the 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.
The translate5 docker installation manual contains a docker-compose configuration file for all services and more advanced information.
# with the execution (and download) of the following docker containers you agree the licenses of the software in the containers! docker run -d --restart unless-stopped --name visualbrowser -p 127.0.0.2:3000:3000/tcp -e CONNECTION_TIMEOUT=600000 -e DEFAULT_IGNORE_HTTPS_ERRORS=true -e MAX_PAYLOAD_SIZE=50mb browserless/chrome docker run -d --restart unless-stopped --name pdfconverter -p 127.0.0.2:8086:8086/tcp translate5/pdfconverter # https://stackoverflow.com/questions/27937185/assign-static-ip-to-docker-container echo 172.17.0.3 visualbrowser 127.0.0.2 pdfconverter
Alias /visual "/PATH_TO_TRANSLATE5/data/visual"
<Directory "/PATH_TO_TRANSLATE5/data/visual">
AllowOverride All
Options Indexes FollowSymLinks
# Options Indexes FollowSymLinks SymLinksIfOwnerMatch
Order allow,deny
Allow from all
</Directory>
- docker pdfconverter & browserless/chrome
- configuration of them!
- apache change needed for browserless/chrome
TO BE DOCUMENTED:
Config
The "runtimeOptions.plugins.VisualReview.shellCommandGoogleChrome" is removed and the docker-url must be set in "runtimeOptions.plugins.VisualReview.dockerizedHeadlessChromeUrl" to continue converting PDFs