Changes between Version 24 and Version 25 of MoveOffTrac


Ignore:
Timestamp:
2025-08-22T07:25:24Z (3 months ago)
Author:
btlogy
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MoveOffTrac

    v24 v25  
    7979     * live: https://www.lafs.eval.latfa.net/
    80802. **IN PROGRESS** - Production (details in #4161):
    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       * ⛔ Extract the data and reconfigure Trac in RO via root access to the legacy server
    93       * ⏸️ OR asynchronous workaround with Meejah
    94       * ⏸️ Rework the redirect/proxy rules to use Forgejo instead of Trac
     81   1. **COMPLETED** - VPS only
     82      * ✅ Infrastructure as Code with CI/CD for !ToFu and Nix in [https://github.com/tahoe-lafs/infrastructure GitHub/ Tahoe-LAFS/infrastructure] repository
     83      * ✅ Hetzner VPS managed from !ToFu code
     84      * ✅ NixOS server managed from Nix code (`webforge`)
     85      * ⛔ DNS records managed from !ToFu code in `tahoe-lafs.org` domain (no proper access - see #4162)
     86      * ✅ WORKAROUND: DNS records managed from !ToFu code in `of.tahoe-lafs.org` subdomain
     87      * ✅ Nightly local and remote backups in place with rsnapshot and !BorgBase
     88      * ✅ Credentials shared via [https://github.com/tahoe-lafs/infrastructure sops] and [https://github.com/tahoe-lafs/infrastructure-pass pass] repositories
     89      * ✅ Forgejo with basic its requirements (DB and mailer) managed from Nix code
     90      * ✅ Forgejo configured with SSO, a [https://forge.of.tahoe-lafs.org/ Tahoe-LAFS] org and some well-known users
     91   2. **PENDING** - Website only with redirect/proxy rules to legacy resources
     92      * ✅ web-landing-page source code with CI/CD up and running on [https://forge.of.tahoe-lafs.org/Tahoe-LAFS/web-landing-page Tahoe-LAFS/web-landing-page]
     93      * ✅ web-landing-page with redirect/proxy rules hosted on `webforge` and managed from Nix code - https://home.of.tahoe-lafs.org/
     94      * ⌛ Manual update of DNS records to expose the web-landing-page (see #4183)
     95      * ➕ the Hall of Fame pages still needs to be "migrated" as a post of a page
     96   3. **TODO** - Issues and wiki hosted by Forgejo
     97      * ⛔ Extract the Trac data and reconfiguration in RO via direct access to the legacy server
     98      * ⏸️ WORKAROUND: asynchronous extraction of Trac data via Meejah
     99      * ⏸️ Rework the redirect/proxy rules from Nix code to expose Forgejo instead of Trac
    95100
    96101== Deliverable 2 - migration plan from Trac to self-hosted Gitea or Forgejo ==
     
    1631682. **IN PROGRESS** - Migration of the static website
    164169   * ▶️ Prospects:
    165      a. [https://docs.codeberg.org/codeberg-pages/ CodeBerg Pages], which will break legacy links (e.g. from !GitHub)
    166      b. [https://www.statichost.eu/docs/ssg-guides/#jekyll StaticHost], which might support redirect/proxy rules and avoid broken links.
     170     a. [https://docs.codeberg.org/codeberg-pages/ CodeBerg Pages] (or !GitHub Pages), which will break legacy links (e.g. from !GitHub)
     171     b. [https://www.statichost.eu/docs/ssg-guides/#jekyll StaticHost], which might support redirect/proxy rules and avoid broken links