jellyfin/jellyfin

Improve config handling

chriscowley asked for this feature 12 months ago — 2 comments

chriscowley commented 12 months ago

Not sure I have a solution, but the configuration could jellyfin could do with an improvement. I would like to use my Kubernetes cluster to host Jellyfin. The "correct" way to configure it would be ConfigMaps or environment for Jellyfin's config. However, currently, the config volume contains 11785 files.

[chris@ovirt01 emby]$ find config/ -type f | wc -l
11785

Even ignoring the config/metadata folder and I have nearly 300 files.

This includes a huge amount of stuff that is simply cache, metadata and defaults. These have no place in the config directory.

By all means this directory can be mounted as a volume, but should be called something else (metadata?). Config needs to come from a (ideally) a single file and/or environment variables.

Terror-Gene commented 11 months ago

I can see where your coming from with the config being cleaned up, but also the config directory I believe should have the bulk of metadata & cache kept in it, as if it wasn’t & if it wasn’t mapped elsewhere (which can be done manually anyway) then it would be bulking up the docker VM environments image which could cause issues. With any docker container I use I expect it to place any bulk it creates into the config directory if it doesn’t have another dedicated directory (e.g. media, or downloads).

Join the discussion!

Sign-in with GitHub to comment