server.coop VS lego

An update: I have found someone for the room in the current house, but that location is very temporary, as it is not conducive to the kind of development I am looking for. What is consuming all my time, and is the reason I have not been actively working on further organizing, is that I am instead working on a prototype for a commercial version of Roomba that automatically plugs itself into a standard power outlet. When I get the very basic prototype of the idea done, I will write up a business plan that details my thoughts on the further steps towards commercialization and post them widely for feedback and additions. As the current location for these ideas is only in my head, I need to get them out in physical form before I can seek collaboration on this endeavor. Hopefully this will be done in a month or two. However, if other people have product ideas that are further fleshed out or are interested in taking over another idea I had that is currently on hold due to lack of interest and time (a cooperative cloud provider https://github.com/TheOtherRealm/server.coop that needs a complete overhaul, or more likely to start from scratch, that replaces the Docker swarm with something better), by all means share!

Self contained but hardly a tiny supply chain attack surface: https://github.com/go-acme/lego/blob/master/go.sum

This ACME client looks promising, but I haven’t tried it yet: https://github.com/go-acme/lego

My favorite method of obtaining certificates is with lets encrypt and LEGO

Caddy where possible, and acme.sh or lego where not.

Depend on host's capability... - lego - dehydrated - caddy - in case it already works as a web server, it will automatically issue and renew certs

u/gregtwallace maybe in the short term until you write your own, you could provide a hook into one of the many ACME client implementations which do DNS-01 and support the majority of major DNS provider APIs out of the box? That would make your (really great!) project much more widely usable.