For me it is writting docker compose files describing my services. I like to test them on my machine before pushing them to the server(s). But I guess that’s my own fault for not using something like portainer or even SSHFS.

What’s the most annoying / painful step for you?

​

  • penghon@alien.topBEnglish
    1·
    1 year ago

    Forgetting how x service works when it is dependent on y service which is dependent on the NAS and the NAS broke and you wonder why everything else is broken too.

  • laser50@alien.topBEnglish
    1·
    1 year ago

    Being to poor to get a proper system, so now I have older Xeon CPU, tons of RAM and a irreplaceable motherboard that is also SFF.

    It only draws 100 watts idle, but that shit adds up :(

    • NavySeal2k@alien.topBEnglish
      1·
      1 year ago

      Yeah, not touching that with a 6 feet pole either… Docker compose does what I need so I’m good thanks.

    • Jacksaur@alien.topBEnglish
      0·
      1 year ago

      Truth.

      I kept an old (Only 8th gen!) CPU around because I thought it’d be easier than a full build for one of my systems.
      Took far too damn long to find a good Mini ITX motherboard for it, let alone one in stock, and in the end the one I did get didn’t even come with a CMOS battery.

      • Dangerous-Ad-170@alien.topBEnglish
        1·
        1 year ago

        This isn’t entirely related to homelab, but I had this exact problem dealing with my mATX gaming PC a few years back. Spilled a beverage on it and somehow the mobo was the only casualty. But it wasn’t that easy to find a six-gen mATX mobo for under $100. If I actually had the time for games, I’d probably use it as an excuse to upgrade everything, but I only keep it around for the occasional indie or Fallout 4 binge or Fortnite session with my son.