2024-06-25, 04:09 AM
Ok, I think I’m understanding this and it sounds like my setup could be far more simplified and streamlined than it is currently. Part of my problem is I was kind of figuring everything out as I went, adding storage when my existing storage maxed out and also going about it with an old school Kodi mentality.
My media is stored on a WD MyCloud with a WD EasyStore drive plugged into the back. That drive and the USB drive plugged into it behaves like a standalone NAS with its own IP address with a dashboard and can be utilized as a Samba, NFS, or UPnP share. I organized my library within those drives by dividing them primarily by audience. Parent Movies, Kid Movies, Common Movies, Parent Shows, Kid Shows, that kind of thing. I added another WD USB drive that plugged into one of my Kodi clients which made it accessible to the other Kodi clients. The problem was I would end up with sources needing to have multiple network paths in order to include all the media spread across different locations. “Parent Movies” was really three discrete paths to three different drives and I wasn’t doing it with the fstab file or anything, so it’s super clunky. I had a MySQL (MariaDB technically I guess) and that was cool when it worked. The thought of being able to manage my library in one spot across multiple Kodi devices with the added benefit of accessing it with non Kodi clients like iOS devices sounded amazing, especially with being able to tweek stuff without affecting the backend itself. The original plan was to put Ubuntu Server on some single board dedicated device and just do it that way, but I ended up getting an older Mac Mini and using that as the host instead with Lubuntu because I wasn’t quite ready for a headless set up yet. Now I have the WD MyBook USB drive, the internal HDD drive of the Mini, the WD MyCloud NAS drive, and drive daisy chained to it all mounted via CIFs in the fstab file. It works. I was able to add everything to the Jellyfin server, but I feel like I have all these redundant samba paths and it seems overly complicated. If I’m understanding what you’re describing, I could partition part of the SDD of the host machine and use that partition exclusively as a preconfigured path to all the different drives for different categories of media to simplify the whole thing?
Also just to make sure I’m understanding the Kodi part, when Jellyfin itself is dialed, I click add source in Kodi as usual, enter my path to the files via SMB/NFS or whatever, and then do I still select what kind of media it is? Does Jellyfin just override the scraper aspect?
My media is stored on a WD MyCloud with a WD EasyStore drive plugged into the back. That drive and the USB drive plugged into it behaves like a standalone NAS with its own IP address with a dashboard and can be utilized as a Samba, NFS, or UPnP share. I organized my library within those drives by dividing them primarily by audience. Parent Movies, Kid Movies, Common Movies, Parent Shows, Kid Shows, that kind of thing. I added another WD USB drive that plugged into one of my Kodi clients which made it accessible to the other Kodi clients. The problem was I would end up with sources needing to have multiple network paths in order to include all the media spread across different locations. “Parent Movies” was really three discrete paths to three different drives and I wasn’t doing it with the fstab file or anything, so it’s super clunky. I had a MySQL (MariaDB technically I guess) and that was cool when it worked. The thought of being able to manage my library in one spot across multiple Kodi devices with the added benefit of accessing it with non Kodi clients like iOS devices sounded amazing, especially with being able to tweek stuff without affecting the backend itself. The original plan was to put Ubuntu Server on some single board dedicated device and just do it that way, but I ended up getting an older Mac Mini and using that as the host instead with Lubuntu because I wasn’t quite ready for a headless set up yet. Now I have the WD MyBook USB drive, the internal HDD drive of the Mini, the WD MyCloud NAS drive, and drive daisy chained to it all mounted via CIFs in the fstab file. It works. I was able to add everything to the Jellyfin server, but I feel like I have all these redundant samba paths and it seems overly complicated. If I’m understanding what you’re describing, I could partition part of the SDD of the host machine and use that partition exclusively as a preconfigured path to all the different drives for different categories of media to simplify the whole thing?
Also just to make sure I’m understanding the Kodi part, when Jellyfin itself is dialed, I click add source in Kodi as usual, enter my path to the files via SMB/NFS or whatever, and then do I still select what kind of media it is? Does Jellyfin just override the scraper aspect?