tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

Rework of the scope and deliverables based on a discussion with Meejah 

[Imported from Trac: page MoveOffTrac, version 6]
btlogy 2024-07-02 16:57:47 +00:00
parent 5a7241cbb3
commit 03f5557319
1 changed files with 10 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
MoveOffTrac.md

@ -19,7 +19,9 @@ The goal of this page is to cover the phases of a project aiming at moving some
2. MUST replace the current landing page (start/home page from the Trac/Wiki): 2. MUST replace the current landing page (start/home page from the Trac/Wiki):
* preferably with a static blog/page generator updated from a Git repo (e.g.: (Go)Jekyll, Hugo) * preferably with a static blog/page generator updated from a Git repo (e.g.: (Go)Jekyll, Hugo)
* possibly with a LAMP stack as discussed: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3892> * possibly with a LAMP stack as discussed: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3892>
3. COULD be used to replace: 3. MUST replace the current binary repository for Tahoe-LAFS releases (<https://tahoe-lafs.org/downloads>)
* by providing at least a similar way to transfer files via ssh
4. COULD be used to replace:
* Github code hosting and review (pull request), keeping only a mirrored clone * Github code hosting and review (pull request), keeping only a mirrored clone
* Github Actions (to avoid leaving secrets in environment variables) * Github Actions (to avoid leaving secrets in environment variables)
* Circle CI (to avoid giving them too many permissions) * Circle CI (to avoid giving them too many permissions)
@ -35,7 +37,6 @@ The goal of this page is to cover the phases of a project aiming at moving some
### Exclusions ### Exclusions
* Binary repository for Tahoe-LAFS releases (<https://tahoe-lafs.org/downloads>)
* Other Trac projects (see [DevInfra](DevInfra)) * Other Trac projects (see [DevInfra](DevInfra))
* Buildbot master instances for some other Trac projects * Buildbot master instances for some other Trac projects
* DARCS SCM for some of the other Trac projects * DARCS SCM for some of the other Trac projects
@ -43,12 +44,16 @@ The goal of this page is to cover the phases of a project aiming at moving some
### Deliverables ### Deliverables
1. A VPS (hosted by Hetzner) providing 4 features powered by NixOS and Gitea: 1. A VPS (hosted by Hetzner) providing the following features powered by NixOS and Gitea:
* a tracking system provisioned with the issues migrated from Trac (same numbers) * a tracking system provisioned with the issues migrated from Trac (same numbers)
* a Wiki system provisioned with the relevant pages migrated from Trac (same names) * a Wiki system provisioned with the relevant pages migrated from Trac (same names)
* a static website replacing the landing page from Trac with the code required for CI and CD * a static website replacing the landing page from Trac with the code required for CI and CD
* a blog post for the Hall of Fame page (if sensible - fallback = static page) * a blog post for the Hall of Fame page (if sensible - fallback = static page)
* a repository defining the VPS it-self and its configuration as code (including the secrets) * a (Git) repository defining the VPS it-self and its configuration as code (including the secrets using sops)
* optionally including the terraform code allowing to manage the related DNS records (if Gandi supports it)
2. A detailed migration plan to handle the transition (DNS changes and/or redirections) 2. A detailed migration plan to handle the transition (DNS changes and/or redirections)
* w/ or w/o terraform code covering the DNS (if Gandi supports it? fallback on manual steps) * documented in a this wiki page
* covering the possible manual steps related to DNS records, HTTP redirections or URL rewriting
* with a (Git) repository including/referring to the tools used to actually migrate
3. An high-level migration plan for the features hosted on the VPS described to be later hosted on Codeberg SaaS (assuming it is possible) 3. An high-level migration plan for the features hosted on the VPS described to be later hosted on Codeberg SaaS (assuming it is possible)
* documented in this wiki page too