I should have clarified I don’t mean for the day, I mean for a week plus.

  • just_another_person@lemmy.world
    link
    fedilink
    arrow-up
    7
    arrow-down
    3
    ·
    19 hours ago
    1. Never put network connectivity on server-class hardware. Low-power devices exist for this reason. Use them.
    2. If you need to access your information remotely when you’re away and it’s running on server-class hardware. Don’t. It’s a needless waste of power.
    3. If you’re talking about accessing your porn collection when you’re on vacation. Don’t. Enjoy your vacation.
    • corroded@lemmy.world
      link
      fedilink
      arrow-up
      3
      arrow-down
      1
      ·
      18 hours ago

      I suppose it depends on your use case, but I would disagree with points 1 and 2. Network connectivity has an effect on your entire network and is absolutely crucial. Pfsense/OPNSense, DNS, etc should always be on server-class hardware. I run these as VM, but I would argue that best practice is to have them on their own bare-metal server-class hardware. File storage is also incredibly important, and even with backups, I don’t want my NAS going down. It also runs on server class-hardware.

      The two items you mentioned are the two items I would be least comfortable running on consumer-grade hardware.