2023-12-12, 06:00 PM
(This post was last modified: 2023-12-12, 06:18 PM by Efficient_Good_5784. Edited 2 times in total.)
Yeah, I just confirmed what TheDreadPirate posted. All playlist files are stored in /config/data/playlists. In this location, you will have multiple folders (depending on your playlist amount) each with .xml files.
If you just want your playlist metadata, just copy all those folder and paste them into the new container in the same location. Then rescan your whole library. Then when the scan is done, your playlists will reappear in the new container.
As for what I suggested about making your config folder external as a host path, this link might help you: https://www.theserverside.com/blog/Coffe...st-machine
You just need to access your synology's shell with SSH (you can enable SSH in synology's control panel), then follow the directions from the link above.
There is another way though:
For number 6, your command would look like this: cp -r config pathToNewHostPathFolder/
Finally, since we're on this topic, I would recommend in the future that you make your config and cache folders external as host paths. Most likely, your Synology NAS is running all HDDs, but in the future if you ever switch to a server that has both HDDs and SSDs, you can mount both your config and cache folders on the faster SSDs to make your Jellyfin server process things faster. Also, it's not really important to copy your cache folder, you can always link to a blank cache folder as the cache will be rebuilt as you use your server.
If you just want your playlist metadata, just copy all those folder and paste them into the new container in the same location. Then rescan your whole library. Then when the scan is done, your playlists will reappear in the new container.
As for what I suggested about making your config folder external as a host path, this link might help you: https://www.theserverside.com/blog/Coffe...st-machine
You just need to access your synology's shell with SSH (you can enable SSH in synology's control panel), then follow the directions from the link above.
There is another way though:
- Stop your old container
- Add a new host path to old container
- Run old container
- In Synology's docker GUI, open the old container and look for how to open a terminal with it
- In the terminal GUI, create a new terimal (will open a bash terminal)
- Use the "cp" command to copy the config folder into the host path folder (-r flag for recursive)
- Go to your host path folder and copy it to any other external folder you want now
For number 6, your command would look like this: cp -r config pathToNewHostPathFolder/
Finally, since we're on this topic, I would recommend in the future that you make your config and cache folders external as host paths. Most likely, your Synology NAS is running all HDDs, but in the future if you ever switch to a server that has both HDDs and SSDs, you can mount both your config and cache folders on the faster SSDs to make your Jellyfin server process things faster. Also, it's not really important to copy your cache folder, you can always link to a blank cache folder as the cache will be rebuilt as you use your server.