search

autobrr / dashbrr

A sleek, modern dashboard for monitoring and managing your media stack services.
https://autobrr.com
GNU General Public License v2.0
43 stars 2 forks source link

Public and internal service URLs #66

Open jfroy opened 3 days ago

jfroy commented 3 days ago

Is your feature request related to a problem? Please describe. I run media apps (autobrr, radarr, etc) on a Kubernetes cluster. They are behind an Ingress-Nginx proxy/load balancer that does https termination. These services's ingress are configured to use oauth2-proxy to provide simple authentication using Ingress-Nginx's external oauth authentication feature. I also deployed dashbrr on this cluster (without oauth2-proxy).

Because of this, dashbrr cannot use the https URL to the media apps since it cannot complete the oauth flow. But it can use the internal service address provided by Kubernetes (e.g. radarr.default.svc.cluster.local).

While this works, it does make the link in the dashbrr frontend for the service unusable.

Describe the solution you'd like Allow configuring separate "frontend" and "API" URLs for each service. The API URL is to be used by dashbrr to query the service, while the frontend URL is to be rendered in the UI for the user.

s0up4200 commented 3 days ago

Hi there! This is already added in the develop branch actually! There's still a few places where access_url doesn't override url, but it will be fixed soon. (See https://github.com/autobrr/dashbrr/issues/51)

I would advice you to also run develop for the time being (or even https://github.com/autobrr/dashbrr/pull/63), as it has several improvements compared to the latest tagged release - with more to come.

Image