| 67 | | 1. Testing |
| 68 | | * Issues and Wiki can be provided by Gitea/Forgejo: |
| 69 | | * https://code.lafs.eval.latfa.net/tahoe-lafs/trac-2024-05-23: 1st migration with many issues |
| 70 | | * https://forge.lafs.eval.latfa.net/tahoe-lafs/trac-2024-07-25: 2nd second migration with a few issues left |
| 71 | | * Known issues (#1170 is a good example): |
| | 67 | 1. Testing (PoC + migration step) |
| | 68 | * VPS provided by Hetzner, mostly defined using Terraform code and deployed by pull request |
| | 69 | * OS based on NixOS, defined using Nix code and deployed by pull request |
| | 70 | * Redirections from legacy to new URLs: provided by Nginx, defined using Nix code and deployed by pull request |
| | 71 | * Issues tracking and Wiki pages: provided by Gitea or Forgejo: |
| | 72 | * https://code.lafs.eval.latfa.net/tahoe-lafs/trac-2024-07-25 |
| | 73 | * https://forge.lafs.eval.latfa.net/tahoe-lafs/trac |
| | 74 | * Todos and known issues (#1170 is a good example): |
| 74 | | * some original links are still not converted and points to tahoe-lafs.org (e.g.: http://!?) |
| 75 | | * more? |
| 76 | | * Website can be provided by Nginx and build from a Git repo hosted by Gitea: |
| 77 | | * https://www.lafs.eval.latfa.net/ |
| 78 | | * The mock is more minimalistic and the PoC site have to be rewored this way |
| 79 | | 2. Production |
| 80 | | * TBD |
| | 78 | * spam mitigation measure required for self-registration (e.g.: OAuth with GitHub/GitLab) |
| | 79 | * Static website: provided by Nginx, build from Jekyll code and deployed by pull request |
| | 80 | * source: https://code.lafs.eval.latfa.net/tahoe-lafs/web-landing-page |
| | 81 | * preview: https://www.lafs.eval.latfa.net/ |
| | 82 | * live: https://www.lafs.eval.latfa.net/ |
| | 83 | * Todos and known issues: |
| | 84 | * the mock is more minimalist and the PoC site have to be reworked this way |
| | 85 | * the Hall of Fame pages till needs to be "migrated" |
| | 86 | 2. Production: |
| | 87 | a) basic only: VPS + OS + NGinx to redirect legacy URLs to services hosted elsewhere |
| | 88 | b) complete: all features from the PoC above |
| 106 | | |
| 107 | | == Pros and Cons of self-hosted vs SaaS == |
| 108 | | |
| 109 | | === Gitea on self-hosted NixOS === |
| 110 | | |
| 111 | | Pros: |
| 112 | | * Links to issues and wiki pages should work (WiP) |
| 113 | | * Attachments are migrated and available |
| 114 | | * Links to comments and attachments work |
| 115 | | * Links to old and authors work (if pre-provisioned) |
| 116 | | * Nearly ready to MoveOffTrac (within one month) |
| 117 | | * Many options to fix content later (e.g.: full access to DB) |
| 118 | | * Website already works with CI/CD |
| 119 | | * CI/CD works like Github and CAN cover all platform |
| 120 | | |
| 121 | | Cons: |
| 122 | | * VPS required (8$/m) |
| 123 | | * Decent baby-sitting required: updates, monitoring and backup/restore (how many h/m?) |
| 124 | | * Poorly scalable, but could perform better than SaaS (DoS protection?) |
| 125 | | * Registration (spam) still need babysitting, but less than for Trac (semi automatic) |
| 126 | | |
| 127 | | Questions or remarks: |
| 128 | | * Maybe LA could manage the self-hosted instance for a short term (e.g.: 1 year)? |
| 129 | | |
| 130 | | === Forgejo on SaaS - Codeberg === |
| 131 | | |
| 132 | | Pros: |
| 133 | | * Smaller VPS (5$/m), but still required for redirection (stateless, maybe possible w/o?) |
| 134 | | * Minimal babysitting: updates and monitoring (how many h/m?) |
| 135 | | * Free of extra charge on Codeberg (20$/user/m on Gitea!) |
| 136 | | * Should be scalable, but performance could be a problem (at least on Codeberg!) |
| 137 | | * Registration (spam) is handled by Codeberg |
| 138 | | |
| 139 | | Cons: |
| 140 | | * Links to authors are broken (likely on purpose - to be verified with Codeberg) |
| 141 | | * Delays MoveOffTrac (unless we agree on 2 steps) |
| 142 | | * Reduced options to fix the content later (e.g.: no access to the DB) |
| 143 | | * Jekyll website needs to be adapted to work on Codeberg (pages) |
| 144 | | * CI/CD works differently from Github/Gitea (but possible) |
| 145 | | |
| 146 | | Questions or remarks: |
| 147 | | * Links to comments are broken: likely a bug, but on which side? |
| 148 | | * Links to attachments are broken but is there any attachment at all? |
| 149 | | * Should we test a free plan on Gitea.com (with CI/CD)? |
| 150 | | * What cost CI/CD on Codeberg vs Gitea.com? (for Win and Mac?) |
