2023-10-17, 02:07 PM
(This post was last modified: 2023-10-17, 02:35 PM by TheDreadPirate. Edited 3 times in total.)
If you are using Jellyfin why would it matter if the media directory is "cluttered" with images and NFO files? You don't see the "clutter" since you are viewing your media with Jellyfin.
Since the media path is not part of the metadata in an NFO, how would Jellyfin make the initial connection between the NFO and the media if it isn't co-located with the media? Additionally, the point of NFOs is easy metadata portability. Having it in a separate directory partially negates that portability. But let's say that NFOs did have the media path and were consolidated in one directory. That's a separate directory you now need to migrate if you change media streaming platforms. Or if you are shuffling your media around or remounting a hard drive, now the NFO is useless as is. You would need to modify all your NFO files.
You can grant Jellyfin write permissions to a directory, but only grant read permissions to your media files. Jellyfin then can write images and NFO files, but can't delete the media and, because the directory still has media, won't be able to delete the directory. I wrote a short bash script to automate this when I add new media.
For the record, Jellyfin will only delete your media if you tell it to or you misconfigure something. One example misconfiguration is if you co-locate your Jellyfin cache with your media. Not sure why you would do this, but someone did do this and found out the hard way that there is a scheduled job that recursively deletes the cache directory.
Since the media path is not part of the metadata in an NFO, how would Jellyfin make the initial connection between the NFO and the media if it isn't co-located with the media? Additionally, the point of NFOs is easy metadata portability. Having it in a separate directory partially negates that portability. But let's say that NFOs did have the media path and were consolidated in one directory. That's a separate directory you now need to migrate if you change media streaming platforms. Or if you are shuffling your media around or remounting a hard drive, now the NFO is useless as is. You would need to modify all your NFO files.
You can grant Jellyfin write permissions to a directory, but only grant read permissions to your media files. Jellyfin then can write images and NFO files, but can't delete the media and, because the directory still has media, won't be able to delete the directory. I wrote a short bash script to automate this when I add new media.
For the record, Jellyfin will only delete your media if you tell it to or you misconfigure something. One example misconfiguration is if you co-locate your Jellyfin cache with your media. Not sure why you would do this, but someone did do this and found out the hard way that there is a scheduled job that recursively deletes the cache directory.