> I wish there were some improvements on doing a highly available self hosted setup. I’m talking plugging 5 machines into a router and power and it just works.

> I wish there were some improvements on doing a highly available self hosted setup. I’m talking plugging 5 machines into a router and power and it just works. Auto healing, redundant backups, etc. I do too! I'm building an open-source system designed for end user self-hosting and one of my goals has been making it as easy as possible to self-host. The two biggest are DNS management and Router port forwarding. I can give you a script that turns a Raspberry Pi into a fully-functional server, but you still need to configure your domain to point to your house, and configure your router to point to the Pi. These require two different solutions. The first would be something like Oauth2 for DNS. I've spoken with the guy running TakingNames who trying to do that, DomainConnect[2] is another approach, but the requirement for service preregistration kills it for consumer self-hosting. For port forwarding, I think we need a self-hoster's router. Something with (at a minimum) a better UI for doing SSL termination and reverse proxy without asking you to understand and nginx config file. Bonus points if a self-hosted service can discover the router and use an Oauth-type flow to do it's own configuration. Once these exist it becomes much more feasible to have a service which does auto fail-over, or redundant backups, etc.. in your basement/living room without additional configuration. [1]: https://takingnames.io/ https://takingnames.io/ [2]: https://www.domainconnect.org/ https://www.domainconnect.org/