2024-01-02, 06:20 PM
(This post was last modified: 2024-01-02, 06:33 PM by Manatee3866. Edited 6 times in total.)
Hi All,
I want to setup Jellyfin server on Synology NAS. I have installed my "Container Manager (previously named Docker)" on NVMe storage pool (Volume 2).
I plan to keep the actual media on Volume1 setup on traditional HDDs while all docker related data on NVMe storage pool to boost the speed of Jellyfin (and other dockers).
I am following this guide and I have already created /Volume2/docker/jellyfin/cache and /Volume2/docker/jellyfin/config folders and my media (movies) are located in /Volume1/media/movies folder
I want to setup Jellyfin server on Synology NAS. I have installed my "Container Manager (previously named Docker)" on NVMe storage pool (Volume 2).
I plan to keep the actual media on Volume1 setup on traditional HDDs while all docker related data on NVMe storage pool to boost the speed of Jellyfin (and other dockers).
I am following this guide and I have already created /Volume2/docker/jellyfin/cache and /Volume2/docker/jellyfin/config folders and my media (movies) are located in /Volume1/media/movies folder
- Is there anything else that I need to do in terms of docker compose or the Jellyfin settings to make the Jellyfin docker make full use of NVMe storage?
- I don't want to use any hardware transcoding so how can I completely disable it so that Jellyfin never tries to transcode any media.
- I intend to setup reverse proxy on Synology (for LAN only) so that I can reach Jellyfin and other containers by URL rather than IP address of NAS and different ports like 8096 for Jellyfin. I plan to follow this guide. Do I have to make any changes inside the Jellyfin docker compose file to make the reverse proxy work?