2 ms·

Self hosting is cool, but my main gripe is all the administration you have to do. I self host at home for content like music, my contacts and password managemen

Self hosting is cool, but my main gripe is all the administration you have to do. I self host at home for content like music, my contacts and password management and my pictures and all that kind of stuff, and I've found a good minimal bullshit way of setting everything up. Self hosting a public presence is a different story. It's not that hard, but it's not set it and forget it. So over time I've offloaded that work onto people that are already doing it. I put my social media presence on a fediverse admin who's doing it already, same with my code hosting. That's really all I need, maybe one day a blog. If I decide to self host all this stuff, I'd probably run a Gemini server, a honk server and cgit for code, if I don't need a lot of collaboration on what I do. If I host for other people my needs would be more, but I don't foresee that.

j45 4y ago
Self-hosting can be made as complex as one wants to make it. Self hosting is best kept simple so it runs like an appliance that can maintain itself. Some people just use dreamhost for the basics already done for them. Lots of one click apps. The OP should have their vps mirrored between more than one service provider. Because it’s not a backup if it’s only one copy or just in one host. It’s not too far fetched to run docker with portainer, or even proxmox on a debian box. Both are solid and I save hundreds of hours if not more in setup and maintenance manually. My past complex hosting experience made me think twice about self hosting. It’s been much easier than it used to be. Very little maintenance unless using brittle languages and cutting edge frameworks. The question is often more about whether there’s inrerest to learn.