I saw this post today on Reddit and was curious to see if views are similar here as they are there.

  1. What are the best benefits of self-hosting?
  2. What do you wish you would have known as a beginner starting out?
  3. What resources do you know of to help a non-computer-scientist/engineer get started in self-hosting?
  • randint
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 month ago

    Can you elaborate on how your backup script re-deploys on new hardware? Sounds very nice to have.

    • schizo@forum.uncomfortable.business
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 month ago

      elaborate

      It’s a really simple script.

      Everything is deployed with a docker compose, and all the docker volume data are bind mounts and, for example, a Jellyfin install would have everything in /stacks/jellyfin.

      The backup script makes a tarball of each service individually (and stops the stack if there’s anything in there doing database things or anything else that might end up being inconsistent by just archiving the filesystem), and uploads them to a S3 storage provider AND burns them to a BluRay.

      The recovery script does the opposite: it downloads and unarchives the data.

      As long as you’re on Linux and have Docker, it should just magically work.

      • randint
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 month ago

        I see! Thanks, will try to back up my docker compose services this way.

        • schizo@forum.uncomfortable.business
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 month ago

          If you write the script yourself, just make sure you test it a couple of times, and preferably with different datasets from different runs.

          I found some edgecase stuff that would have prevented a restore even after I had tested it successfully (some permission issues due to changes in containers and whatnot were resulting in less than the expected data being archived and restored) a couple of times.