- cross-posted to:
- opensource@programming.dev
- privacy@programming.dev
- selfhost@lemmy.ml
- cross-posted to:
- opensource@programming.dev
- privacy@programming.dev
- selfhost@lemmy.ml
This is a post about the whole path it took me to get from the old days of Google Music to Navidrome, and some views on the topic. Maybe this is something that interest you, in this case give a read.
All feedback is welcome.


My only wishlist for Navidrome is SSO support besides reverse-proxy/forward-auth headers. I’ve got that setup with Authentik and Nginx Proxy Manager, but having to make specific path exceptions or duplicates with rewrites for apps/API, rather than just being able to generate an app password/token in Navidrome for an app to use, definitely is annoying. I don’t think I saw a write-up anywhere but I figured out what was needed.
Man I eventually stopped fighting that hurdle and just changed the login screen to say “Broken-ass auth” so I remember that one is different. I’m the only person using it at my house and recently went back to a car with a CD player and USB port for infotainment (such a refreshing change after a decade and a half of screens in my face) so I haven’t bothered to go back to fix it.