I’m not the guy you replied to.
I originally stored my music in Plex and used Plexamp. I have a large playlist downloaded from youtube which caused horrible performance issues in Plexamp. Navidrome is pretty much a read-only service. It can only read metadata from the files, not add any or manage them. For me this feels safer to expose to the internet since my docker container only has read-only access to all of my files. Even if someone broke into the service for some reason, they couldn’t do anything to my files.
I don’t know if jellyfin has similar performance issues with large playlists since I already had navidrome set up by then.
Thanks! I don’t have too much music on it yet, I guess, so not sure on the performance. I do like that read only approach, though. Currently I’m running just the regular jellyfin app on my Mac. What made you use it in docker? It sounds like in Linux it’s a safeguard to prevent dependency issues but I don’t think that’s really a factor on mac
Mostly ease of management. I have a server on which I run multiple applications. If I don’t need something anymore, I can just purge the container. The directories used by that container are clearly listed in my docker-compose file so I never have to wonder whether I purged everything that is now unnecessary.
It also makes it very easy to deploy a new service.
