Changes between Version 13 and Version 14 of MoveOffTrac

Timestamp:

2024-09-09T13:53:12Z (10 days ago)

Author:

btlogy

Comment:

--

MoveOffTrac

@@ -80 +80 @@
    * TBD
 
-== Deliverable 2 - migration plan from Trac to self-hosted Gitea/Forgejo ==
+== Deliverable 2 - migration plan from Trac to self-hosted Gitea (or Forgejo) ==
 
 1. Testing
@@ -93 +93 @@
    3. tahoe-lafs.org to new VPS + redirect/proxy to legacy
 
-Choice:
-  * short or middle term intermediate? meejah says self-hosted OF SaaS w/o intermediate : new legacy link to take care or not.
-
-== Deliverable 3 - high-level migration plan from Forgejo to Codeberg ==
+== Deliverable 3 - high-level migration plan from self-hosted to SaaS - Codeberg ==
 
 1. Testing
@@ -104 +101 @@
      * all links to contributors are broken (likely because Codeberg does not allow this? maybe the user needs to be local and in the org first?! )
      * all links to comments are broken (likely because they use the ID from the source!)
-     * all the link to attachement are broken
+     * all the link to attachment are broken
 2. Production
    * TBD
@@ -110 +107 @@
 == Pros and Cons of self-hosted vs SaaS ==
 
-=== self-hosted Gitea ===
+=== Gitea on self-hosted NixOS ===
 
 Pros:
 * Links to issues and wiki pages should work (WiP)
-* Links to comments work
-* Links to attachments work
-* Links to authors work (if pre-provisioned)
-* Nearly ready to MoveOffTrac
+* Attachments are migrated and available
+* Links to comments and attachments work
+* Links to old and authors work (if pre-provisioned)
+* Nearly ready to MoveOffTrac (within one month)
 * Many options to fix content later (e.g.: full access to DB)
 * Website already works with CI/CD
@@ -126 +123 @@
 * Decent baby-sitting required: updates, monitoring and backup/restore (how many h/m?)
 * Poorly scalable, but could perform better than SaaS (DoS protection?)
+* Registration (spam) still need babysitting, but less than for Trac (semi automatic)
 
-=== SaaS Forgejo on Codeberg ===
+Questions or remarks:
+* Maybe LA could manage the self-hosted instance for a short term (e.g.: 1 year)?
+
+=== Forgejo on SaaS - Codeberg ===
 
 Pros:
-* Smaller VPS (5$/m), but still required for redirection (statless, maybe possible w/o?)
-* Minimal baby-sitting: updates and monitoring (how many h/m?)
+* Smaller VPS (5$/m), but still required for redirection (stateless, maybe possible w/o?)
+* Minimal babysitting: updates and monitoring (how many h/m?)
 * Free of extra charge on Codeberg (20$/user/m on Gitea!)
 * Should be scalable, but performance could be a problem (at least on Codeberg!)
+* Registration (spam) is handled by Codeberg
 
 Cons:
-* Links to comments are broken
-* Links to attachments are broken (or no attachement at all?)
-* Links to authors are broken (likely on purpose)
+* Links to authors are broken (likely on purpose - to be verified with Codeberg)
 * Delays MoveOffTrac (unless we agree on 2 steps)
 * Reduced options to fix the content later (e.g.: no access to the DB)
-* website needs to be adapted to work on Codeberg
+* Jekyll website needs to be adapted to work on Codeberg (pages)
 * CI/CD works differently from Github/Gitea (but possible)
 
-Remarks:
+Questions or remarks:
+* Links to comments are broken: likely a bug, but on which side?
+* Links to attachments are broken but is there any attachment at all?
 * Should we test a free plan on Gitea.com (with CI/CD)?
-* What cost CI/CD on Codeberg vs Gitea.com (for Win and Mac?)
+* What cost CI/CD on Codeberg vs Gitea.com? (for Win and Mac?)