Self-hosting

3665 readers

7 users here now

Hosting your own services. Preferably at home and on low-power or shared hardware.

Also check out:

founded 3 years ago

MODERATORS

poVoq@slrpnk.net

sam_uk@slrpnk.net

Where to begin? (sh.itjust.works)

submitted 3 weeks ago* (last edited 3 weeks ago) by MrScottyTay@sh.itjust.works to c/selfhosting@slrpnk.net

10 comments fedilink hide all child comments

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?

you are viewing a single comment's thread
view the rest of the comments

[–] greengnu@slrpnk.net 0 points 3 weeks ago (1 children)

You write up a procedure for the setup of your server and any virtual machines contained within.

Using declarative Distros makes the procedure shorter and easier to maintain in the long run.

Then you use it to setup your system (fixing issues in your procedure along the way)

Then wipe and do it again (this time should be done without issue or you may need another spin)

Then slowly grow your documentation and what services you have running.

[–] MrScottyTay@sh.itjust.works 1 points 3 weeks ago

That's a good idea to run through it a few times before using it proper, thanks.