Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve config handling #38

Closed
chriscowley opened this issue Dec 11, 2018 · 1 comment
Closed

Improve config handling #38

chriscowley opened this issue Dec 11, 2018 · 1 comment
Labels
build Issues with the build process

Comments

@chriscowley
Copy link

chriscowley commented Dec 11, 2018

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.

@anthonylavado anthonylavado added the build Issues with the build process label Dec 12, 2018
@joshuaboniface
Copy link
Member

I think this has been gradually solved by various cleanups. Currently on 10.0.1, there are only 30 files in the config dir:

joshua@test5 /etc/jellyfin $ find . -type f -printf c | wc -c
30

Considering this solved; if not please let me know @chriscowley !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Issues with the build process
Projects
None yet
Development

No branches or pull requests

3 participants