Add support for defining both host/port and webapp URL per App instance

[mrslippers]

Would it be possible to add an optional field to each App configuration to specify the base URL for that app that is used when presenting links to users in Hunt Manager? This would be useful for setups where containers are on the same network and can talk directly, but traffic from users is routed through a reverse proxy. For background here's my setup:

I currently use Nginx, specifically LinuxServer's Swag container, as a reverse proxy in front of my arr stack to provide user access, and the arr apps that need to talk to each other are on the same Docker network. This means there's effectively two ways for a connection to to Sonarr to be successful.

1. A container on the same docker network would use a base URL of http://sonarr:8989
2. Anything outside the docker network would have to use https://sonarr.somedomain.com.

Overseerr does something similar where you device the host/port which it uses for API connectivity to your stack, but any links that are presented to the user will use the Web App URL parameter that is optionally defined.

[Admin9705]

ya can look into this. thanks for the suggest