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?

  • @ctry21@sh.itjust.works
    1•3 days ago

    I think portainer is probably the best tool for this since you can easily go in and pause/start services as required. Just make sure to go into the containers on portainer and check the restart policy is set to “unless stopped” so you don’t get unwanted restarts after a reboot or anything like that.

    I don’t think portainer has any automation options but you could possibly write a short cron script to run docker compose down in the directory of each compose file to shut them down once a month, and pair that with the uptime kuma container to get a notification when your containers are down so you can go into portainer and restart the ones you still need. Though I’ve never had any real issue with running lots of containers at once – there’s 20 on my raspberry pi right now and it’s still got just over a gigabyte of RAM left.