Feature Request - Immich "internal" and "external" URL config

[Cebrain]

Hi,

i have an feature request for the immich integration.
I want to specify different URLs for the for the internal integrationto the immich docker container as http://immich_app:2345 and for the external URL

The problem is dawarich has the nice feature to got directly from a trip to the immich application and check out all photos in this timeframe.

At the moment dawarich forwards to the internal container
http://immich_app:2345/places......
It would be nice if i could specify a correct external URL, such as
https://immich.example.com/places.....

[Freika]

I don't see this as a feature in the future, but still will leave it open, just to not lose this idea

[Cebrain]

This means, you configure the external Proxy Address in the Dawarich App?
This means you must go through the proxy to immich? This isn't the best approach for performance and also you have an additional dependency, which i would like to eliminate.

[xathon]

I'd also like to add that there should be a way to differentiate between how Dawarich talks to Immich and how a user accesses Immich. The internal communication is exactly what the Docker networks are for, to avoid having to use a proxy which is where the user would come from.

[Freika]

@Cebrain yes, I'm using reverse proxy to access my Immich, it's accessible behind Tailscale and I always have it on

@xathon if it brings more complexity to the app and more surface for potential bugs, it might be not a good idea, considering no feasible benefits will be provided with the implementation

[Cebrain]

@Freika my opinion would be it will be a security benefit and makes it would be less complex.

With the current setup and official DNS name, the container needs to talk with the external DNS (get DNS information), then talks with the proxy and then it finally goes to the immich instance.
So at the moment there could be also a problem with the DNS or the Proxy. Also all traffic will go through the proxy instead of internal network traffic and bad proxy config could also cause problems.
If i could specify a internal and external URL the container only needs to talk with immich it self and does not bother about DNS or proxy information.

At the end as xathon mentioned, it would be more the "Docker Way" to have an internal and external network.
But i also understand if this could mean a bigger rework of flows and is not feaseable in the near future.

[aarondoet]

For me it is impossible to have both Dawarich able to use the Immich API and have the Immich links provided by Dawarich usable as is. Immich is exposed to the internet but it has authentication on the reverse proxy level. Dawarich won't be able to access Immich through the reverse proxy because it isn't authenticated for the reverse proxy. But I myself am not inside the docker network so I can't use the address that Dawarich is using to bypass the reverse proxy.

I don't see how this option would really add complexity or potential for bugs, there probably is something along the lines of const url = new URL("/search/query?...", config.immichUrl), that would just need to use a different base url for the request itself and for displaying the url to the user. And adding another field to the config should not be hard to do.