| 70 | |
| 71 | == Pros and Cons of self-hosted vs SaaS == |
| 72 | |
| 73 | === self-hosted === |
| 74 | |
| 75 | Pros: |
| 76 | * Links to issues and wiki pages should work (WiP) |
| 77 | * Links to comments work |
| 78 | * Links to attachments work |
| 79 | * Links to authors work (if pre-provisioned) |
| 80 | * Nearly ready to MoveOffTrac |
| 81 | * Many options to fix content later (e.g.: full access to DB) |
| 82 | * Website already works with CI/CD |
| 83 | * CI/CD works like Github and CAN cover all platform |
| 84 | |
| 85 | Cons: |
| 86 | * VPS required (8$/m) |
| 87 | * Decent baby-sitting required: updates, monitoring and backup/restore (how many h/m?) |
| 88 | * Poorly scalable, but could perform better than SaaS (DoS protection?) |
| 89 | |
| 90 | === SaaS === |
| 91 | |
| 92 | Pros: |
| 93 | * Smaller VPS (5$/m), but still required for redirection (statless, maybe possible w/o?) |
| 94 | * Minimal baby-sitting: updates and monitoring (how many h/m?) |
| 95 | * Free of extra charge on Codeberg (20$/user/m on Gitea!) |
| 96 | * Should be scalable, but performance could be a problem (at least on Codeberg!) |
| 97 | |
| 98 | Cons: |
| 99 | * Links to comments are broken |
| 100 | * Links to attachments are broken (or no attachement at all?) |
| 101 | * Links to authors are broken (likely on purpose) |
| 102 | * Delays MoveOffTrac (unless we agree on 2 steps) |
| 103 | * Reduced options to fix the content later (e.g.: no access to the DB) |
| 104 | * website needs to be adapted to work on Codeberg |
| 105 | * CI/CD works differently from Github/Gitea (but possible) |
| 106 | |
| 107 | Remarks: |
| 108 | * Should we test a free plan on Gitea.com (with CI/CD)? |
| 109 | * What cost CI/CD on Codeberg vs Gitea.com (for Win and Mac?) |