-
Notifications
You must be signed in to change notification settings - Fork 33
IP/Port Config of Machinery #5
Comments
hey @wcomartin, thanks for your advice. My docker knowledge is limited, do you see any solution to resolve this matter? |
Hey sorry I haven't responded earlier, I will see if i can put together a PR to fix, do you accept PRs? |
ofcourse @wcomartin , awesome! |
I was just thinking about this a bit more, and I think that adding the variables to Docker could be a quick fix, but I think a better long term solution may be to have config in the app to specify the machinery IP/Port this would make it easier to add multi server support to one Web instance later. for example instead of having a proxypass to the machinery in the nginx config (https://github.com/kerberos-io/web/blob/master/docker/web.conf#L27) make this route configurable in the app/config files. Just a thought i had. |
@cedricve I added the two ENV vars to the web docker in the web repo, which branch would you like me to make a PR to? develop? |
perfect |
It would be nice if the Web Docker had a config variable for the Machinery IP and Port
Instead of using the hostname
machinery
and a static port 8889this make using multiple docker container pairs very difficult, I had to bash into the container to override the hosts file and the port in the nginx config.
The text was updated successfully, but these errors were encountered: