[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):

 Concentrating on the wider point: my understanding of the entire "get off
 Trac" effort is to ''reduce'' self-hosting.

 Instead, it seems like this all points to an '''increased''' burden:
 continuing to self-host a Trac replacement, hosting a Wiki / landing-page
 replacement, hosting redirection infrastructure and the addition of self-
 hosted/managed DNS as well. All while keeping (some of) the email self-
 hosted (the difficulties of self-hosting email was a main reason e.g. the
 mailing-list is hosted elsewhere: email simply wasn't getting through
 consistently).

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