Jellyfin and/or plex will do that, and it's what I'm using.
The BF has an account and a music library, and I have a different one.
Jellyfin and/or plex will do that, and it's what I'm using.
The BF has an account and a music library, and I have a different one.
It’s especially nice to use either of these on Linux because you can use symlinks to have the server think the audio files are in more than one place without using any extra storage space.
Just be cautious when moving or backing up the files, things like rsync and bakula have specific flags needed to preserve symlinks.
You could go even further and use hard links. That way, you can have two paths pointing to the same data on the partition, with the space getting cleaned up only after all references to it are removed.
Absolutely!
If anyone is interested here's a great thread on it
Good point!
Jellyfin, Ampache, Plex are your best bets.
Checkout plexamp as your client if you use plex
Finamp on Android if you are using Jellyfin
They recently got a huge update that overworked the ui and it's absolutely brilliant. Don't know if it's out of beta yet but I've been using it for over a month and it works absolutely flawlessly.
I have the same problem with navidrome so I've written a new Opensubsonic server in Rust with a permision model. You can check it out here: https://github.com/vnghia/nghe
I know you didn't want to, but I'll bet two navidrome instances will be faster and lighter than JF or Plex.
Navidrome is still the best music server, even with all of its limitations. For what it's worth, the developer is currently working on features intended to support multiple music libraries. It's going to happen eventually.
I use Plexamp for that, Jellyfin does it too. You can assign libraries per user quite easily.
So for 3 users you might have 4 libraries, one per user then a shared library they all have access to.
I use Jellyfin. I think in your use case, each user would be setup have their own library. You can enable or disable library on a per user basis as will as a per client basis.
Downside is that the default web interface isn’t great as a music player. It does the job but it’s not great.
Other hand, multiple music-first clients exist for a lot of different platforms. Odds are good you can find a client that suits how you listen to music.
Edit: said collection when I meant library.
I like finamp as my android music client for jellyfin
Me too! Not much to look at but it’s a great player on iOS. On Linux, I like SonixD.
I like the Ultrachrome CSS mod. It doesn't massively change the interface - but it looks a bit nicer imo
Navidrome can have multiple users. I don't know that they can each have separate libraries though.
It doesn’t afaik :/
I need also LDAP or Oauth2 support, is there a good software with this feature as well?
Jellyfin can ldap
Ampache with subsonic for app support.
I like Subsonic. The interface is a bit dated but it supports multiple users and has excellent android apps.
@jaykay@lemmy.zip Navidrome supports multiple users. The issue for you is to merge collections, then?
The issue I have is that all users see the same music (all of it). I would like to be able to “disable/enable” songs/albums per user
Why not use a combined library if I may ask? This would be similar to things like Spotify or tidal but then self hosted.
Actually... you're f right. Why do I create problems for myself, just add everything to one pot and let users fav/star the ones they want and use the "Favourites" folders. Thanks
They can also make playlist for them self. And hey as a bonus they might discover other songs they like.
Funkwhale?
I think Funkwhale is dead isn't it?
Seems to just be hosting issues https://www.reddit.com/r/Funkwhale/comments/1dlrsqn/funkwhaleaudio_down/
Well, this post got deleted too. But the website is back up it seems.
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!