[GH-ISSUE #208] IP address necessary for rendering FrontEnd? #202

New issue

Closed

opened 2026-02-27 15:55:37 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 15:55:37 +03:00

Owner

Originally created by @s1rk1t on GitHub (Dec 21, 2018).
Original GitHub issue: https://github.com/RD17/ambar/issues/208

Wondering if it's possible to have AMBAR's docker .yml file have something other than the ip address for where the FrontEnd is hosted?

For instance, is there some way I can have line 113 of the .yml file read:
- api=http://somedomain/ambar instead of -api=http://ipaddress:portnumber ?

Originally created by @s1rk1t on GitHub (Dec 21, 2018). Original GitHub issue: https://github.com/RD17/ambar/issues/208 Wondering if it's possible to have AMBAR's docker .yml file have something other than the ip address for where the FrontEnd is hosted? For instance, is there some way I can have line 113 of the .yml file read: `- api=http://somedomain/ambar` instead of `-api=http://ipaddress:portnumber` ?

kerem closed this issue

2026-02-27 15:55:37 +03:00

kerem commented

2026-02-27 15:55:38 +03:00

Author

Owner

@Jachimo commented on GitHub (Dec 21, 2018):

I was likewise surprised by this. It looks like that line specifies the connection between the web frontend and the API container, which could be done over the Docker internal network? Unless there are other components that need to hit the API besides the web frontend, it seems like you could just use the internal network and specify the container name. But maybe I'm missing something; I have not stopped my instance to test it.

@Jachimo commented on GitHub (Dec 21, 2018): I was likewise surprised by this. It looks like that line specifies the connection between the web frontend and the API container, which could be done over the Docker internal network? Unless there are other components that need to hit the API besides the web frontend, it seems like you could just use the internal network and specify the container name. But maybe I'm missing something; I have not stopped my instance to test it.

kerem commented

2026-02-27 15:55:38 +03:00

Author

Owner

@isido993 commented on GitHub (Jan 8, 2019):

@Jachimo you can't use the Docker internal network since the front end always runs in user's browser which is never inside the Docker net.

@isido993 commented on GitHub (Jan 8, 2019): @Jachimo you can't use the Docker internal network since the front end always runs in user's browser which is never inside the Docker net.