[tahoe-lafs-trac-stream] [Tahoe-LAFS] #4162: Infrastructure as Code to manage DNS configurations

[Tahoe-LAFS]

#4162: Infrastructure as Code to manage DNS configurations
------------------------------------+-----------------------
     Reporter:  btlogy              |      Owner:
         Type:  enhancement         |     Status:  new
     Priority:  normal              |  Milestone:  undecided
    Component:  dev-infrastructure  |    Version:  n/a
   Resolution:                      |   Keywords:  IaC
Launchpad Bug:                      |
------------------------------------+-----------------------

Comment (by meejah):

 Can we not use HTTP-01 challenge for certificates? This does not require
 DNS changes, and is the default for Let's Encryp AFAIK.


 Adding self-hosting of email (and DNS?) seems like it goes the wrong way
 here; much of the "problem" being solved is that maintenance of self-
 hosted systems hasn't gone well for Tahoe-LAFS. Self-hosted CI rotted a
 while ago (i.e. nobody updated BuildBot, or its runners), and getting rid
 of self-hosted wiki+issues is much of the current "ask" here.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/4162#comment:17>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage