-
Notifications
You must be signed in to change notification settings - Fork 53
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
Comments
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 |
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. |
@aleksasiriski is correct; basically, I just simplifed the docs by saying we need both instead of going through every possible subfolder. To put it another way... |
/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?
The text was updated successfully, but these errors were encountered: