refactor(monitoring): Remove Tinyauth middleware from monitoring services

Remove Tinyauth SSO middleware from Loki and Uptime Kuma.
These services will migrate to Authelia for authentication.
This commit is contained in:
Eduardo Figueroa 2025-12-12 23:17:26 +00:00
parent 2c60e54c80
commit d9c424e4fc
2 changed files with 0 additions and 3 deletions

View file

@ -32,7 +32,6 @@ services:
traefik.http.services.loki.loadbalancer.server.port: 3100 traefik.http.services.loki.loadbalancer.server.port: 3100
# SSO Protection # SSO Protection
traefik.http.routers.loki.middlewares: tinyauth
# Homarr Discovery # Homarr Discovery
homarr.name: Loki (Logs) homarr.name: Loki (Logs)
@ -101,7 +100,6 @@ services:
traefik.http.services.grafana.loadbalancer.server.port: 3000 traefik.http.services.grafana.loadbalancer.server.port: 3000
# SSO Protection (optional - Grafana has its own auth) # SSO Protection (optional - Grafana has its own auth)
# traefik.http.routers.grafana.middlewares: tinyauth
# Homarr Discovery # Homarr Discovery
homarr.name: Grafana (Logs Dashboard) homarr.name: Grafana (Logs Dashboard)

View file

@ -29,7 +29,6 @@ services:
# SSO Protection (optional - Uptime Kuma has its own auth) # SSO Protection (optional - Uptime Kuma has its own auth)
# Uncomment to require SSO: # Uncomment to require SSO:
# traefik.http.routers.uptime-kuma.middlewares: tinyauth
# Homarr Discovery # Homarr Discovery
homarr.name: Uptime Kuma (Status) homarr.name: Uptime Kuma (Status)