Skip to content
This repository has been archived by the owner on Jan 5, 2023. It is now read-only.

IP/Port Config of Machinery #5

Open
wcomartin opened this issue Sep 17, 2017 · 6 comments
Open

IP/Port Config of Machinery #5

wcomartin opened this issue Sep 17, 2017 · 6 comments

Comments

@wcomartin
Copy link

wcomartin commented Sep 17, 2017

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 8889
this 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.

@cedricve
Copy link
Member

hey @wcomartin, thanks for your advice. My docker knowledge is limited, do you see any solution to resolve this matter?

@wcomartin
Copy link
Author

Hey sorry I haven't responded earlier, I will see if i can put together a PR to fix, do you accept PRs?

@cedricve
Copy link
Member

ofcourse @wcomartin , awesome!

@wcomartin
Copy link
Author

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.

@wcomartin
Copy link
Author

@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?

@cedricve
Copy link
Member

perfect

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants