Profiles.xml

[DenyAll]

Minor enhancement.

Would it be possible to have a button on Serviio Console (probably on the Status tab) to force Serviio to reload Profiles.xml. This would help avoid the issue of users not restarting their Serviio Service after editing profiles.

Another possible enhancement I have thought about is to have an optional file "User Profiles.xml" that if it exists, is loaded after the standard profiles. This will allow users to store their custom profiles and mods in a separate file, so that when an update of Serviio comes along, they don't have to go back on an make their modifications to "Profiles.xml" (which is overwritten every update).

[atc98092]

OK, that's entirely too logical...

Splendid idea. Depending on what the core program does after loading the profiles, it shouldn't be too difficult. However, if he does a bunch more program loading after the profiles are loaded, it might take some significant coding changes. Nothing is impossible (almost...)!

[grolschie]

I concur. Possibly the user's profile file could take precedence when matching device user-agents or friendly names, incase the default profile gets loaded instead of one's own custom profile.

Funnily enough, I just came to post a feature request about splitting-up the Profiles.xml for a few reasons:

1. The current config is already pretty long, which makes it hard to read/find stuff, hence by being able to put profiles into their own files, it would make life that bit easier - for those editing them at least!
2. At the minute, the built-in profiles seem to be more series rather than device based, and I'm guessing (in part) that's because of concerns around an explosion of profiles making the profiles.xml file huge!
3. It could provide a nicer way of separating what people should and shouldn't edit, e.g. the default profile could be in a file that should never be edited.
4. It would allow people to put their own profiles into separate files, so that they are easy to keep/migrate when upgrading Serviio, e.g. the Serviio installer can add/delete/update its own, and leave the rest alone.

Perhaps this could be achieved using a directory based approach. There could be a root profiles.xml, which has some XML nodes in that define the subdirectories (with a priority level) to look in for profiles. For example, that root profiles.xml could contain the default profile, and reference three other directories: Series Based Profiles (Low Priority), Device Based Profiles (Medium Priority) and User Defined Profiles (Highest Priority).

Note: You could perhaps avoid always loading all of the profiles too (instead just lazy loading what you need) by having a kind of list.xml in each subdirectory, which for each profile contains a name, the search pattern(s), and path to its config file. I guess doing so would enable the config files to be easily stored in a directory hierarchy, which might be useful, if eventually you end-up with a lot of config files.

I just came to post a feature request about splitting-up the Profiles.xml for a few reasons:
.... It would allow people to put their own profiles into separate files, so that they are easy to keep/migrate when upgrading Serviio.

Thanks James

I wanted to ask for the same feature: to have my own Profile in a separated file.
When upgrading Serviio today, it's a huge and risky job to merge my old customized Profiles file with the new stock Profiles.xml

Regards
Pierre

[DenyAll]

FYI: I also raised this as a bitbucket issue/request in February - see https://bitbucket.org/xnejp03/serviio/i ... r-profiles.
Also I must have been having a blonde moment, as I raised the second part of this request in another topic... see also: viewtopic.php?f=3&t=16053

Perhaps it would also be worth linking to this topic in the ticket?

[DenyAll]

Good idea - done.

Definitely like the idea of a users profile file as this would - from a user's perspective - make life simpler.

Having just started using Serviio this would be my first request. I'm currently using Mezzmo on my PC which has separate profile files by device ID & this works very well - if you make a mistake in an individual profile then only that one fails to load. And obviously any upgrades won't overwrite your amendments.

[grolschie]

FYI: I also raised this as a bitbucket issue/request in February - see https://bitbucket.org/xnejp03/serviio/i ... r-profiles.

This is a good idea. I have voted on the ticket.