Multi-user support in terms of datasource and song-library

[TwizzyDizzy]

Hi folks,

as of now, you have a user concept of "admin" and "listener". Maybe there could be a third kind of user account, let's call it "uploader" for now, that is able to upload music, too. I can image several scenarios where this would be a nice feature (e.g. people sharing a flat and also sharing a sonerezh instance).

Every account would have its own song library.

One could implement that as follows:

• admin defines a "base path" for sonerezh to look for music (example: /music)
• every "uploader" user would have a folder below that "base path" (example: /music/my-uploader-user)
• admin would be able to globally update the database
• "uploader" user would be able to update the database only for their "directory" (read: only for their database)

One would have to implement some kind of scheduler that collects database indexing requests and process them sequentially (in order to not overload the server with multiple concurrent indexing jobs).

There could be some status indicator in the user interface as to whether the scheduled indexing requests have finished (for example some green or read light or some notification: "your database update has been scheduled", "your database update has finished").

The scheduler could be implemented as a cron job, as pointed out by @Knah-Tsaeb in https://github.com/Sonerezh/sonerezh/issues/2#issuecomment-76938415.

Cheers Thomas

[lGuillaume124]

What a kill-feature! I like it, but I don't know if we will have time to implement it one day :/

I keep this open ;)

[MightyCreak]

In the same idea, when I installed Sonerezh, I thought each users could define its own music library. It was quite a deception when I saw it wasn't the case.

My idea was to bind the "music" directory of each of my ownCloud users to their account in Sonerezh.

Since we don't have the same tastes, I'd rather not get all the songs in one big library.