2020-12-02, 16:44
New to the forums but have been skulking the boards for many years troubleshooting small issues. Thanks for the great posts and maintenance 
About 6 months ago I finally decided to make my media storage more accessible and add some redundancy so I began by duplicating my video storage to a second server and also have that duplicated media serve the second location. Seems easy enough since I had used Kodi before and thought I understood how scraping information works. But as soon as I started adding more user this became a bit more complicated and I feel like I am duplicating my efforts and want to fix it before the users at the second location begin to use the data.
The Question: "Should I be using .NFO files or online scrapers if I have multiple users, reading the same data, who need to have their own start/stop/resume points? And when creating users should I be setting either "media info, media source" to anything other than "Separate?".
My Setup: I have multiple users at my location ( me, spouce, kids1, kid2 ) multiple age groups for kids, multiple Kodi instances (2 TV's, 2 phones, 1 pc) I duplicate my "mediasources.xml, advancedsettings.xml" and drop it into "userdata" and "userdata/profiles/userName/" on each device, and I am running a single MySQL server in docker. The MySQL database is tagged for each user
The Friction: Each time I want to update my media I have to log into each users profile, scrape, then go through the files and fix any fan art, banners, and title naming for each users account. Yes, I only need to do it in once per user because each device picks up the changes as expected (since the changes are stored in the MySQL database). How can I scrape once keeping a point of truth and have each user see that information change but still maintain their own watched/resume points of that data?
Ideally what I want in the end is to use the LinuxServer dot io "kodi-headless" container so I can automate my media updating in one place and have that populate for all my users. I am also fine if I have to perform this action at each location1 and location2 (location2 uses their own database anyways and my users don't need to be present on their Kodi instance). Each night my location1 sends a snapshot of any new data to location2 (this is why I am wondering if .NFO is my answer.... is it that simple?).
About 6 months ago I finally decided to make my media storage more accessible and add some redundancy so I began by duplicating my video storage to a second server and also have that duplicated media serve the second location. Seems easy enough since I had used Kodi before and thought I understood how scraping information works. But as soon as I started adding more user this became a bit more complicated and I feel like I am duplicating my efforts and want to fix it before the users at the second location begin to use the data.
The Question: "Should I be using .NFO files or online scrapers if I have multiple users, reading the same data, who need to have their own start/stop/resume points? And when creating users should I be setting either "media info, media source" to anything other than "Separate?".
My Setup: I have multiple users at my location ( me, spouce, kids1, kid2 ) multiple age groups for kids, multiple Kodi instances (2 TV's, 2 phones, 1 pc) I duplicate my "mediasources.xml, advancedsettings.xml" and drop it into "userdata" and "userdata/profiles/userName/" on each device, and I am running a single MySQL server in docker. The MySQL database is tagged for each user
My media is split up into separate shares over the network allowing me to pick and choose the datasets each user can access (movies, tv, kids-movies, anime-movies, anime-tv), for my account I want everything but my spouse only cares about "movies, tv, kids-movies", and the kids only need access to kids-movies, and as they get older I will add datasets and use age restriction to control the data they see.xml:<name>justenoughlinuxVideo</name> <name>justenoughlinuxMusic</name>
The Friction: Each time I want to update my media I have to log into each users profile, scrape, then go through the files and fix any fan art, banners, and title naming for each users account. Yes, I only need to do it in once per user because each device picks up the changes as expected (since the changes are stored in the MySQL database). How can I scrape once keeping a point of truth and have each user see that information change but still maintain their own watched/resume points of that data?
Ideally what I want in the end is to use the LinuxServer dot io "kodi-headless" container so I can automate my media updating in one place and have that populate for all my users. I am also fine if I have to perform this action at each location1 and location2 (location2 uses their own database anyways and my users don't need to be present on their Kodi instance). Each night my location1 sends a snapshot of any new data to location2 (this is why I am wondering if .NFO is my answer.... is it that simple?).
