I'm looking for some under the hood info - from advanced users that have built a multi-client environment.
My existing system is pretty basic, as I like to keep things simple, and in the event of a problem I don't have to muck through a maze of "how did I do this again?"
I have a Synology NAS - that provides all the storage for my media files. Using all the built-in 'add video' sources within Kodi - linked to my NAS. I've also enabled a MariaDB10 app, on the NAS to support the MySql feature within Kodi - so all my clients (multiple FireTV & PCs (Windows,MAC)) sync to the same dB.
This all works quite well, however a bit complex configuration on each client to maintain if I make the same change or add a source, etc.
So here's where my questions begin...
I've installed Emby Server on one of my Synology NAS boxes, actually, this particular one is an Xpenology device. I chose that one because it has much more HP than my official Synology boxes. I've also purchased a lifetime Emby account.
I've built a Kodi (18.1) client on one of my Fire TV televisions - from scratch. Installed the basic Addons that I require for my use ... OpenSubtitles, Trakt, Lyrics & Backup. I've also just installed Emby/con - addons.
After running and testing - to the Kodi local dB all seems to be working well. I'm not sure how the updates to the local client dB updates, and if there is by directional flow when it comes to Trakt data, and partially watched positions, etc...
Would it be better to switch to using the Mysql as a common dB source for my clients as I did before? or just stick to the Kodi local dB file dB? I'm thinking using the Mysql dB would be a bit redundant and just complicate things. That I should just let Emby do all the dB work, and keep the local client dBs updated.
any HELP, feedback and or comments would be welcome.
So far I'm pretty impressed with Emby server.
Edited by tcichowicz, 16 March 2019 - 12:28 PM.