Closed raphpa closed 1 year ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I suppose a chmod after creating the files would fix the issue!
@raphpa @marouamghar created a pr for this. I believe this would fully resolve your pain points?
@Silvenga i think so. I looked at the PR, are you planning on converting it to a mod?
Not sure why chowning takes that much time, but a RUN chmod -R 666 /usr/share/jellyfin/web
in Dockerfile
would also let the plugins inject itself.
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
TBH @marouamghar - I stopped using the LSIO image since I needed to debug the internals of JellyFin. I've built my own https://github.com/silvenga-docker/jellyfin-debug.
Through this, I've separated the frontend and backend and I'm having Nginx rewrite the index.html file to inject the script in.
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
This issue is locked due to inactivity
Is this a new feature request?
Wanted change
Changing the owner of the included web interface files to the given PUID/PGID that jellyfin runs with.
Reason for change
The plugin Jellyscrub needs a custom script on the player page to work. For that it injects itself into the index.html file on jellyfin start. This only works if the container is started with root for PUID/PGID, else the jellyfin process is not allowed to modify the index.html file.
Proposed code change
Changing the owner of /usr/share/jellyfin/web to PUID/PGID on container start.