It seems there's a tracking issue here, but it seems stalled: https://github.com/go-gitea/gitea/issues/1612
> If you have a server with SSH access, just init a bare repo in a directory, push to that, and you're ready to go. No web UI needed.
Used to do that years ago for my personal projects. Honestly does the trick.
Gitea gets you: a nice GitHub-like web GUI, including for stuff like managing users; 2FA; some integrations; web hooks without having to add git-hooks to all your repos; and extremely-useful-to-some-projects features like git-lfs support.
If you don't want or need those things, bare git repos are fine and certainly easier to support (not that Gitea's that hard, though a few issues/PRs I've noticed have caused me more than a little concern about the overall quality of the project).
Re:GitHub incident 2022-03-23
by encryptluks2 on Wednesday March 23, 2022 @12:06PM
(#30779915)
But by using GitHub for "collaboration" you are sacrificing decentralization.
Absolutely, and I genuinely hate that.
But for new open source projects of mine the ease of contribution and user expectation of a github repository are a trade-off worth making even so (I also maintain a self hosted master git repo that I consider the source of truth to -me- but these days it syncs from, rather than to, github, just because of the trade-offs involved).
Re:GitHub incident 2022-03-23
by encryptluks2 on Thursday March 24, 2022 @07:18AM
(#30788360)
And in return you are sacrificing your code and contributors to a Microsoft-based privacy policy. GitLab is better but still not ideal.
After all, you don't even need Gitea for pure Git hosting. If you have a server with SSH access, just init a bare repo in a directory, push to that, and you're ready to go. No web UI needed.
The reason I'm still using GitHub is not code hosting. It's collaboration.