| 71 | | 1. Testing/PoC (completed and retired): |
| 72 | | * VPS provided by Hetzner, mostly defined using OpenToFu code and deployed by pull request |
| 73 | | * |
| 74 | | * |
| 75 | | * |
| | 69 | 1. **DONE** - Testing/PoC (retired): |
| | 70 | * ✅ VPS provided by Hetzner, mostly defined using !ToFu code and deployed by pull request |
| | 71 | * ✅ OS based on NixOS, defined using Nix code and deployed by pull request |
| | 72 | * ✅ Redirections from legacy to new URLs: provided by Nginx, defined using Nix code and deployed by pull request |
| | 73 | * ✅ Issues tracking and Wiki pages: provided by Gitea or Forgejo: |
| 78 | | * Todos and known issues (#1170 is a good example): |
| 79 | | * tables are not correctly converted to MD |
| 80 | | * some original links are still not converted and points to tahoe-lafs.org (e.g.: http://!?) |
| 81 | | * authors need to be created as user before the migration to link contributions to their profile |
| 82 | | * spam mitigation measure required for self-registration (e.g.: OAuth with GitHub/GitLab) |
| 83 | | * Static website: provided by Nginx, build from Jekyll code and deployed by pull request |
| | 76 | * ✅ Static website: provided by Nginx, build from Jekyll code and deployed by pull request |
| 87 | | * Todos and known issues: |
| 88 | | * the mock is more minimalist and the PoC site have to be reworked this way |
| 89 | | * the Hall of Fame pages till needs to be "migrated" |
| 90 | | 2. Production: |
| 91 | | a. basic only: VPS + OS + NGinx to redirect legacy URLs to services hosted elsewhere |
| 92 | | b. complete: all features from the PoC above |
| | 80 | 2. **IN PROGRESS** - Production: |
| | 81 | 1. **PENDING** - Website only: VPS + OS + NGinx + website + redirect/proxy rules to legacy resources |
| | 82 | * ✅ Hetzner VPS is up and running on NixOS (webforge.of.tahoe-lafs.org) |
| | 83 | * ✅ Nightly local and remote backups in place with rsnaphot and !BorgBase |
| | 84 | * ✅ Nix and !ToFu source code with CI/CD up and running on [https://github.com/tahoe-lafs/infrastructure GitHub/Tahoe-LAFS/infrastructure] |
| | 85 | * ✅ Forgejo is up and running with 6 well-known users and 3 SSO providers on https://forge.of.tahoe-lafs.org/ |
| | 86 | * ✅ web-landing-page source code with CI/CD up and running on [https://forge.of.tahoe-lafs.org/Tahoe-LAFS/web-landing-page Forgejo/Tahoe-LAFS/web-landing-page] |
| | 87 | * ✅ web-landing-page up and running on https://home.of.tahoe-lafs.org/ |
| | 88 | * ✅ Credentials are shared via [https://github.com/tahoe-lafs/infrastructure sops] and [https://github.com/tahoe-lafs/infrastructure-pass pass] repositories |
| | 89 | * ⛔ Waiting for the DNS records to be changed in #4183 |
| | 90 | * ➕ the Hall of Fame pages till needs to be "migrated" |
| | 91 | 2. **PENDING** - All features from the PoC above: issues and wiki hosted by Forgejo |
| | 92 | * ⏸️ Steps described in #4161 (will require new data dump from Trac) |
| | 93 | * ➕ Known issues (#1170 is a good example): |
| | 94 | * tables are not correctly converted to MD |
| | 95 | * some original links are still not converted and points to tahoe-lafs.org (e.g.: http://!?) |
| | 96 | * authors need to be created as user before the migration to link contributions to their profile |
| 100 | | 1. Migration plan (completed): |
| 101 | | 1. Create an API token on Forgejo with Read access on repositories own by the [https://forge.of.tahoe-lafs.org/Tahoe-LAFS Tahoe-LAFS org] |
| 102 | | 2. Use the [https://codeberg.org/repo/migrate migration tool] on !CodeBerg to migrate the repository/ies |
| 103 | | 3. Archive the repository/ies on Forgejo |
| 104 | | |
| 105 | | 2. PoC (completed): |
| 106 | | * Issues and Wiki pages originally hosted on Trac |
| 107 | | * Outcome: https://codeberg.org/Tahoe-LAFS/trac-2024-07-25 |
| 108 | | * Caveats: |
| 109 | | * all links to contributors are broken (likely because !CodeBerg will not allow this) |
| 110 | | * all links to comments are broken (likely because they use the ID from the source!) |
| 111 | | * all the link to attachment are broken (likely because the migration tool does not cover them - yet) |
| 112 | | * Code, issues, pull-requests and CI/CD for the Static website |
| 113 | | * Outcome: https://codeberg.org/Tahoe-LAFS/web-landing-page |
| 114 | | * Caveats: |
| 115 | | * CI runner does not support (yet) docker (can be work around with local installation of ruby+gems) |
| | 104 | 1. **DONE** - Migration of the Forgejo repository/ies: |
| | 105 | * ✅ Plan: |
| | 106 | 1. Sign-in to [https://forge.of.tahoe-lafs.org Forgejo] and create an API token on Forgejo with Read access on repositories own by the [https://forge.of.tahoe-lafs.org/Tahoe-LAFS Tahoe-LAFS org] |
| | 107 | 2. Sign-in to !CodeBerg as a member of the [https://codeberg.org/Tahoe-LAFS Tahoe-LAFS] org |
| | 108 | 3. Use the [https://codeberg.org/repo/migrate migration tool] on !CodeBerg to migrate the repository/ies from [https://forge.of.tahoe-lafs.org Forgejo] |
| | 109 | 4. Archive the migrated repository/ies on [https://forge.of.tahoe-lafs.org Forgejo] |
| | 110 | * ✅ PoC (examples): |
| | 111 | * Issues and Wiki pages originally hosted on Trac (archived) |
| | 112 | * Outcome: https://codeberg.org/Tahoe-LAFS/trac-2024-07-25 |
| | 113 | * Caveats: |
| | 114 | * all links to contributors are broken (likely because !CodeBerg will not allow this) |
| | 115 | * all links to comments are broken (likely because they use the ID from the source!) |
| | 116 | * all the link to attachment are broken (likely because the migration tool does not cover them - yet) |
| | 117 | * Code, issues, pull requests and CI/CD of the new static website (archived) |
| | 118 | * Outcome: https://codeberg.org/Tahoe-LAFS/web-landing-page |
| | 119 | * Caveats: |
| | 120 | * CI runner does not support (yet) docker (work around possible with local installation of ruby+gems) |
| | 121 | 2. **IN PROGRESS** - Migration of the static website |
| | 122 | * ▶️ Prospects: |
| | 123 | a. [https://docs.codeberg.org/codeberg-pages/ CodeBerg Pages], which will break legacy links (e.g. from !GitHub) |
| | 124 | b. [https://www.statichost.eu/docs/ssg-guides/#jekyll StaticHost], which might support redirect/proxy rules and avoid broken links. |
