Hi, so I’ve ended up bagging myself a big supermicro server. I’m wanting to try out a little bit of everything with it, but one thing I really want is to be able to have services that haven’t been used for a bit to stop or sleep. And then to wake up again or start up on request, rather than me having manually stop and start services. Is that a thing?

I know of portainer and whatnot, but I’m wondering if anyone has any advice on this.

I’m planning on putting debian on it i think (unless someone can convince something else is better suited - i usually use arch on my personal devices btw 😜)

Also i know some basics on raid but I’ve only ever messed with raid0 with usb drives on a pi. I have 8 bays but 2 are currently vacant. What is the process of just adding an extra drive to a raid, or replacing one that already exists?

  • tofu
    3·
    2 days ago

    If you want to have VMs as well, Proxmox is the to-go thing in selfhosting. Maybe your supermicro even has two network interfaces and can have a virtualized firewall or the like.

    Not quite sure about your services go sleep thing. Ideally, services won’t use much CPU while idling, but certainly RAM. You can probably build something like you described, but it’s mostly not “a thing” afaik.

    • MrScottyTay@sh.itjust.worksOPEnglish
      3·
      2 days ago

      Ah so i might be thinking leaving a service running is worse than it actually is then?

      The motherboard has two networks ports and a card with another two. There’s also some fibre ports but i imagine I’ll never end up using them haha.

      I don’t actually really know much about firewalls at all yet though