• 0 Posts
  • 60 Comments
Joined 2 years ago
cake
Cake day: July 18th, 2023

help-circle
  • Yep, bind mount the data and config directories and back those up. You can test a backup by spinning up a new container with the data/config directories.

    This is both easy and generally the recommended thing I’ve seen for many services.

    The only thing that could cause issues is breaking changes caused by the docker images themselves, but that’s an issue regardless of backup strategy.




  • Some of the commands I use a lot for debugging containers, in case you go down that route:

    • docker run --rm -it --entrypoint bash <image_name>
    • This command let’s you enter a docker image with bash so you can test commands and treat it like a temporary VM. Great way to see how the image is setup
    • docker exec -it <container_name>
    • This let’s you enter a running container with bash. A great way to inspect why something might not be working or check mounted volumes, etc.

  • Once you know how to use docker/containerization it’ll be the only way you want to deploy applications. Most popular applications will also have good guides on how to setup/config the container, but sometimes you’ll need to read up on docker and Linux to figure things out.





  • I think the easiest way would be to have two vlans on your local network. One that is connected to the internet and another that is local only. I think you’d have to switch networks when wanting to access the jellyfin server in that instance, but would negate the main issue, which is your VPN.

    Edit: that’s about the most secure you can get I think. If you bought a different physical router to host it, you’d have about as secure a setup as possible.