@cambridgeport90@indieweb.social @blacklight @koherecoWatchdog I'm also interested in being enlightened on why Gitea over GitLab!
@blacklight @cambridgeport90@indieweb.social @koherecoWatchdog Thanks for the comprehensive answer!
@blacklight @cambridgeport90 @biguenique That’s a lot of good reasons there. I didn’t know #Gitlab had incompatibilities with standard git. That should get a big spotlight because #git is designed to be inherently portable and decentralized. Sounds like Gitlab is using tactics from Microsoft’s playbook.
@koherecoWatchdog @cambridgeport90 @biguenique the change to the "recommended" version of git has actually happened quite recently https://docs.gitlab.com/ee/install/installation.html#git.
Note the "The Git version provided by Gitaly may contain custom patches required for proper operation" out of Microsoft's textbook.
@biguenique @cambridgeport90 @koherecoWatchdog the main reason was performance and requirements. Gitlab took 3-4 GB of RAM on my server, and it was a mix of several fat Ruby services. Gitea only takes 150-200 MB,way less disk space, and only one service running.
Then there was the fact that Gitlab recently broke git and gitaly now provides its own executable. This is another no go for me: a git server should be able to deal with the vanilla git, not push its own implementation.
Lastly, Gitlab's recent desperate moves towards profitability and its main focus on paying business customers and cloud hosting reminded me that it's bad to use a product made by a company that doesn't prioritize your use-case.