• Illecors@lemmy.cafe
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    2
    ·
    edit-2
    1 day ago

    Yea, I should definitely write something up so bollocks like this does not proliferate.

    • AtariDump@lemmy.world
      link
      fedilink
      arrow-up
      3
      arrow-down
      1
      ·
      1 day ago

      Please do.

      Be sure to also put how much time people can realistically expect to spend on each step (including offsite backup and recovery).

      • Routhinator@startrek.website
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        1
        ·
        1 day ago

        Been running my own server for 15 years. I need to put about 20 hours maintenance a year in for updates. I have the whole thing automated as a helm chart using PVCs with cert-manager for auto-renewal and the node just runs k3s as a single node.

        That’s a lot of extra layers, but the layer of seperation between the host and the services makes it very easy to automate all the pain away.

        • liara@piefed.ca
          link
          fedilink
          English
          arrow-up
          3
          ·
          1 day ago

          20 hours per year is far too many hours of my time, and you’re past the point of having to spend the time architecting it. You also have the operational costs of whatever you decide to host on, along with your backups.

          Imo, paying $100 or even $200 a year is a steal in comparison

          • Routhinator@startrek.website
            link
            fedilink
            English
            arrow-up
            2
            ·
            1 day ago

            I pay $300 for 3 years with SSD nodes.

            I never have to worry about the company hosting my mail going corrupt, being sold, or being coerced into giving access to my data without just cause.

            You undervalue the cost of maintaining the trust with a provider