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?

  • solariplex@slrpnk.net
    1·
    1 day ago

    Jerboa crashed mid-comment so i’ll be brief.

    Save yourself pain and increase your happiness by

    • using btrfs or zfs (snapshots, checksum and self-healing is great)
    • using declarative approach rather than imperative, and keep a copy of configs elsewhere (I accidentally nuked my system multiple times, you should expect to do the same)
    • keeping backups. If zfs, https://github.com/jimsalterjrs/sanoid and syncoid are great https://discourse.practicalzfs.com/t/setting-up-syncoid-for-offsite-backup/1611
    • have an extra tiny machine running the same system and workloads, where you test potentially risky stuff before doing so on the prod server
    • metrics solutions like prometheus and grafana are your friend