2023-12-14, 11:03 PM
(This post was last modified: 2023-12-14, 11:13 PM by Efficient_Good_5784. Edited 3 times in total.)
(2023-12-14, 09:47 PM)GarrickWinter Wrote: At this point I think you're done?Yeah, that's all you have to do to transfer your server information.
With Docker, as long as you keep your config and media files in an external folder location, updates to Jellyfin just require you to remount the folders to the new container.
If the new Jellyfin version requires a rework to the config file structure, it will apply those to your config folder location.
Therefore, it's helpful to make a copy of the config folder before running it with the new Jellyfin server version in case you want to revert back a server version.
Personally, I have a central folder location where I make a new subfolder each server version that comes out. I copy and paste the latest of my config folder into this new subfolder and link that to the new container in Docker.
Just make sure to turn off the container/server as you're copying the config folder to avoid copying a file as it's being written to by the server.
Also, if you want to see what the "cp" command is doing in the terminal in real-time, add the -v flag (for verbose).
So "cp -rv folder1/ folder2/" will print on the screen exactly what it's copying from folder1 to folder2 in real-time.
Same thing for the "mv" (move) command. Adding a -v flag will show that it's doing a "cp" (copy) to the new folder, followed by a "rm" (remove) on the old location to delete it there.