[Feature] Separation of PUBLIC_URL into container-specific and client-specific URLs

[mnahinkhan]

Is there an existing issue for this feature?

• Yes, I have searched the existing issues and it doesn't exist.

Feature Description

It seems to me that the PUBLIC_URL I provide in the docker compose config needs to be reachable from both the user's browser, as well the container running the server application. This probably works fine in cases where your PUBLIC_URL is open to public, but for my specific use case (and I suspect for many selfhosters) this is not the case, as we like to keep our home network inaccessible from the outside world.

For example, in my use case, I use Tailscale to access my homework remotely. I have set up my public DNS (something like "resume.MYDOMAIN.com" to point to my Tailscale address, which is accessible only when I'm connected to the Tailscale network.

As a result, their URL is accessible from my browser on any machine that is connected to my Tailscale network, but the container running chromium for example would not be able to reach the resolved IP (of resume.MYDOMAIN.com)

But yet the other containers are accessible using their docker network names ("app", "minio", etc) from the "chrome" container, so I was thinking it should be possible to separate these things (i.e. the client uses PUBLIC_URL to generate links to the resume etc but the server, specifically the chromium container, uses a different address like "http://app:3000" to connect to the app container).

The same arguments apply for the STORAGE_URL variable and "minio".