4 ms·
Gitea does not use Github because the software can't handle their load requirements, but because they started using GH before Gitea had all the features they ne
by tylersmith 4y ago
Gitea does not use Github because the software can't handle their load requirements, but because they started using GH before Gitea had all the features they needed. They are actively working on hosting Gitea on Gitea, with the last piece being an importer to move over all their GH data.
Blender seems to have been ok manually migrating some things and abandoning other things, since they weren't likely to ever get a Phab->Gitea importer anyways.
https://github.com/go-gitea/gitea/issues/1029 https://github.com/go-gitea/gitea/issues/1029
- bawolff 4y agoHow much traffic could they possibly have? Quite frankly either gitea has absolutely terrible scalability or something else is off here. Edit: i misread the parent comment. My bad.
- yamtaddle 4y agoHuh? It isn't because of inability to handle load, that they host on GH. Gitea performs alright. It can serve surprisingly-heavy traffic from a potato-tier VM with a SQLite backend (assuming the host network can keep up with it, anyway). Not Github-scale (but Github has... a lot of traffic, including a whole lot of write traffic) but quite a bit, and that's with basically the worst-possible hosting situation for handling high load.
- techknowlogick 4y agoThat's correct. It is not due to load, gitea.com already has most of the projects repos migrated already, just not the main one due to ratelimits and exporting all the issues. Gitea.com has thousands of users, and multi-TB traffic monthly on a fairly modest setup. Disclaimer: I'm one of the members of the technical oversight committee of the Gitea project, and am employed to work on Gitea.
- tylersmith 4y agoTbf my comment was phrased a bit ambiguously, but I couldn't think of anything less ambiguous.