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

Docker cache is mentioned in the setup documentation, but not explained #62

Open
temotodochi opened this issue Feb 25, 2023 · 3 comments

Comments

@temotodochi
Copy link

/cache directory is mentioned in the setup documentation but its use is not explained in docker context except that it must be mounted on transcoder. Where? What mount point? Where is that set?

@aleksasiriski
Copy link
Contributor

aleksasiriski commented Feb 25, 2023

If you're using Jellyfin inside a docker container then I suggest you use my image which isn't directly associated to this repo (there's also a repo for the worker, if you have issues open them there.

To answer your question: Joshua explained that a worker needs access to Jellyfin /config and /cache on the same mount paths as Jellyfin itself, but my testing showed that only /config/transcodes and /config/data/subtitles are needed.

@seang96
Copy link

seang96 commented Oct 28, 2023

After adding a new plugin to my setup today, I found out a use for the cache directory being shared for rffmpeg processes and the jellyfin server. Jellyscrub uses rffmpeg to generate the images, and stores it temporarily in the cache directory, then once all images are generated, it stores it into the destination folder. Since the plugin runs on the jellyfin server, it wont pickup the images generated on rffmpeg.

@joshuaboniface
Copy link
Owner

@aleksasiriski is correct; basically, I just simplifed the docs by saying we need both instead of going through every possible subfolder. /cache is needed for pre-extracting images and subtitles, which is why it's mentioned.

To put it another way... rffmpeg does not mangle paths. If Jellyfin gives it a media path like /mymedia/myshow/file.mkv, that file must be present at that precise location on the rffmpeg target as well. Same with a config path of say /config/transcodes/myfile.m3u or whatever.

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

No branches or pull requests

4 participants