Redmine ticket 20743 will introduce a UI component that makes it easier to integrate a proxy server into the system. Until then, these notes show a workaround.
Each Altus container will have a config directory in the host server that stores various non-volatile components (show profiles, for example). One of the files in this directory is the license.json file. After the proxy server is installed, the license.json file will need to have the IP address of the server hosting the proxy. In a system with access to the internet, the format of this file could be
{"licenses":["ALTUS-xxxx-wwww-zzzz-yyyy-ssss"],"servers":["173.233.141.18:42131"]}The IP of the proxy-server host should be added in front of the public web based IP. So….
{"licenses":["ALTUS-xxxx-wwww-zzzz-yyyy-ssss"],"servers":[“192.169.2.4:42131”,"173.233.141.18:42131"]}or
{"servers":[“192.168.2.4:42131”,"173.233.141.18:42131"]}The path for the file would depend on how the container was set up. The original telos script places the container information in /opt/telos/{name_of_container}/config/
The Portainer-based system appears to place in the following path
/var/lib/docker/volumes/{containerName}_config/_data/
You should restart the container once you have made the change.
NOTE: This is rather hackish.
How do you introduce a variable so it can be introduced through compose or env file???
The very hackish approach…
sudo nano /var/lib/docker/volumes/studioA_config/_data/license.json
{make needed edits, save, exit; restart the container}
Troubleshooting:
If the proxy server is hosted on the same machine that hosts the containers, there will be issues with a macvlan container accessing the host machine. This is a well documented issue within docker. The macvlan-bridge should remedy this issue, but if not, other system routes could be introduced to help, such as this forum post.