System administrators

Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

This is installation is for new installations. If you upgrade from an existing installation see translate5 > 5.8.0 - needed visualreview to docker migration

Install translate5 and its services

get docker-compose.yml

get docker-compose.production.yml - change if needed

create .env:

CONTAINER_REGISTRY_BASE=translate5
MYSQL_USERNAME=translate5
MYSQL_PASSWORD=translate5
APP_HOST=t5docker.localdev
COMPOSE_FILE=docker-compose.yml:docker-compose.production.yml

call docker-compose up

Important note for paid or private customer specific plug-ins

VisualReview

In order to use visualreview:

  • get a docker hub token from MittagQI
  • login to docker hub with that
  • get docker-compose.visual.yml
  • add to .env docker-compose.yml:docker-compose.visual.yml:docker-compose.production.yml
  • check docker-compose.production.yml and comment in the visual related entries.
  • follow below general steps

General steps for paid/private plug-ins

In order to use paid or private customer specific plug-ins, follow the normal installation. If all is up and running request the installer package containing all private plugins from mittagqi. You will receive an URL pointing to the package.zip.

Go into the translate5 docker container:

docker-compose exec php bash
t5 status 
# now you should be in /var/www/translate5
wget URL_TO_YOUR.zip
./install-and-update.sh YOUR.zip
t5 service:autodiscovery -s


This steps will be improved in the near future, so that private plug-ins are registered via the config and pulled automatically.

SSL Offloading

SSL Offloading to an external LB is possible, the LB must support / enable websockets.

  1. Configure Translate5 as it would have SSL (server.protocol = https://) and run autodiscovery to configure messagebus correctly.
  2. In the proxy container of translate5 modify /etc/nginx/conf.d/server.conf and duplicate the /ws/ location block with /wss/.

The last step is needed since the /wss/ location block is normally in the ssl-server.conf which is not used since SSL is offloaded.

  • No labels