Currently the API_HOST parameter is providing the UI with the external host and port on where to redirect API calls to. We have observed that this is a bit brittle since it tends to prevent sharing of docker compose files.
I can think of two ways ways to solve this (but there might be a nicer way that I'm overlooking):
the UI could run into the same server as the API
The UI server had a small proxy that redirects certain calls to the internal API server.
Both allow the usage of an absolute relative uri for the API calls in the UI.
Currently the API_HOST parameter is providing the UI with the external host and port on where to redirect API calls to. We have observed that this is a bit brittle since it tends to prevent sharing of docker compose files.
I can think of two ways ways to solve this (but there might be a nicer way that I'm overlooking):
Both allow the usage of an absolute relative uri for the API calls in the UI.