[tahoe-lafs-trac-stream] [Tahoe-LAFS] #4161: Move off Trac - Execution - Forgejo

[Tahoe-LAFS]

#4161: Move off Trac - Execution - Forgejo
------------------------------------+------------------------
     Reporter:  btlogy              |      Owner:  btlogy
         Type:  task                |     Status:  new
     Priority:  normal              |  Milestone:  undecided
    Component:  dev-infrastructure  |    Version:  n/a
   Resolution:                      |   Keywords:  movofftrac
Launchpad Bug:                      |
------------------------------------+------------------------

Comment (by btlogy):

 To whoever will read this [https://lists.tahoe-lafs.org/pipermail/tahoe-
 dev/2025-August/010133.html update] from the mailing list, we (at Least
 Authority) are waiting for our SSH public [https://github.com/tahoe-
 lafs/infrastructure/blob/3684be02678fbf624e43338399847438a5ece481/tf/core/providers.tf#L27-L28
 keys] to be authorized to access the current Linode server so we can:

 1. (at least) extract the Trac data ourselves w/o unnecessary back-and-
 forth (reducing frictions and downtime)
 2. (preferably) re-configure the NGinx with a new virtualhost (legacy
 .tahoe-lafs.org)
 3. (if possible) re-configure the main Trac project to "read-only" once
 the migration is completed

 This in addition to write access to the DNS records which is detailed in
 #4162

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