@@MrJagergeek when I started the series of apps in Synology, I was mounting the folders in a different way to showcase to people what volumes are in Docker. I created a video talking about improvements and I expressed that file transfers from downloads to end folder would be faster if you had everything under one volume named “HTPC.” Check that video out, if you haven’t. It’s after the setup of Bazaar or so in the arrs playlist.
@@techbytetips I will review those. Unfortunately, I was already committed to this install when I realized this. Now, at the adding media part, Jellyfin cannot see my actual paths to videos, which is (/volume1/video/Movies, /volume1/video/Music Videos, etc.) It seems that XML setting of media wasn't correct for my scenario. My configuration is: source: /volume1/video target: /Media
@@MrJagergeek It shouldn't matter if you have a different folder structure. You just have to adjust it. In my case the source is: /volume1/HTPC/Media Inside that I have folders for all media types: /volume1/HTPC/Media/Anime /volume1/HTPC/Media/TV /volume1/HTPC/Media/Movies /volume1/HTPC/Media/Music Just make sure to map it appropriately to your container. For example, if your top folder is /volume1/video and inside if you have all your folders containing your media: /volume1/video/TV /volume1/video/Movies /volume1/video/Music then you just need to mount the /volume1/video to your Jellyfin instance like you mentioned: /Media When you add your libraries, look for the sub folders inside the /Media directory inside the container. It should work as long as you are giving the proper user to the container. Make sure that the user is able to read/write to the folders inside the Synology permissions. 1026/100 is usually the first user you create in the NAS when you set it up and it is an administrator by default.
@@techbytetips Appreciate the responses. I think I need to do more 'homework'. I had Jellyfin up and running in a container only, but decided to start over and use the project method described here. Now I fear there are 'ghosts' in the machine of previous installs as the web page sometimes shows two servers - one named jellyfin, and the other a string of random numbers. I also need to become knowledgeable of the differences in settings in YAML vs. container settings vs. inside the dashboard. All seem related, yet different. I'll deeper.
@@MrJagergeek If you were running it as a container, it shouldn't have left anything. If you were trying to install it directly in Linux, then that's a possibility. Using the projects vs using the old way, makes no real difference. It's just writing code in YAML versus manually creating the configurations.
![Install Kapowarr using Docker in a Synology NAS [Video Request]](http://i.ytimg.com/vi/U-gXREugSMQ/mqdefault.jpg)
![Install Kapowarr using Docker in a Synology NAS [Video Request]](/img/tr.png)
Thank you so much!
Me funcionó!!
Que bueno que te haya ayudado el video.
at 6:40 you refer to HTPC folders and media as though you've already talked about it. It seems I'm missing a prerequisite video perhaps?
@@MrJagergeek when I started the series of apps in Synology, I was mounting the folders in a different way to showcase to people what volumes are in Docker. I created a video talking about improvements and I expressed that file transfers from downloads to end folder would be faster if you had everything under one volume named “HTPC.” Check that video out, if you haven’t. It’s after the setup of Bazaar or so in the arrs playlist.
@@techbytetips I will review those. Unfortunately, I was already committed to this install when I realized this. Now, at the adding media part, Jellyfin cannot see my actual paths to videos, which is (/volume1/video/Movies, /volume1/video/Music Videos, etc.) It seems that XML setting of media wasn't correct for my scenario.
My configuration is:
source: /volume1/video
target: /Media
@@MrJagergeek It shouldn't matter if you have a different folder structure. You just have to adjust it.
In my case the source is:
/volume1/HTPC/Media
Inside that I have folders for all media types:
/volume1/HTPC/Media/Anime
/volume1/HTPC/Media/TV
/volume1/HTPC/Media/Movies
/volume1/HTPC/Media/Music
Just make sure to map it appropriately to your container.
For example, if your top folder is
/volume1/video
and inside if you have all your folders containing your media:
/volume1/video/TV
/volume1/video/Movies
/volume1/video/Music
then you just need to mount the /volume1/video to your Jellyfin instance like you mentioned: /Media
When you add your libraries, look for the sub folders inside the /Media directory inside the container.
It should work as long as you are giving the proper user to the container.
Make sure that the user is able to read/write to the folders inside the Synology permissions.
1026/100 is usually the first user you create in the NAS when you set it up and it is an administrator by default.
@@techbytetips Appreciate the responses. I think I need to do more 'homework'. I had Jellyfin up and running in a container only, but decided to start over and use the project method described here. Now I fear there are 'ghosts' in the machine of previous installs as the web page sometimes shows two servers - one named jellyfin, and the other a string of random numbers. I also need to become knowledgeable of the differences in settings in YAML vs. container settings vs. inside the dashboard. All seem related, yet different. I'll deeper.
@@MrJagergeek If you were running it as a container, it shouldn't have left anything. If you were trying to install it directly in Linux, then that's a possibility. Using the projects vs using the old way, makes no real difference. It's just writing code in YAML versus manually creating the configurations.