111–120 of 124 posts
Gogs, the project Gitea has been forked off, works just as well. As far as I can see there's no technical reason to prefer the fork over the original. Judging from Github stars, Gogs is also vastly more popular.
Edit: This list have been created on best efford, if you find any wrong information a pull request is always welcome.
> Open Source: It’s all on GitHub! There's some level of irony in a GitHub alternative that's hosted on GitHub.
It is an awesome product, I really want to try it a bit more at home later in the evening. Don't you think it could be a good idea that considering it is to self host git projects, to self host your own project? I mean, why don't you use your own product?
It's probably a cost question, to my knowledge gitea.io is a github pages website. The only running cost is really the domain. Running the git service is probably a bit expensive and you loose the network effect of github. They could probably migrate to gitlab though.
Does Gitea still not have a good mechanism for backup and restore? I wanted to move away from Gogs but this is a show stopper for me.
I'd be more convinced to give it a try if Gitea's repository itself was hosted on Gitea rather than on GitHub.
> Open Source: It’s all on GitHub! There's some level of irony in a GitHub alternative that's hosted on GitHub.
Self-hosting also takes resources such as time and money, and not all open source projects have the latter.
Is there a hosted version of Gitea? Would it be possible to host it and offer unlimited repos for let's say $5/mo as a service?
Just wondering if it's time to start to decouple the client and the server. I did that with mail and use a native client only, and hosting a git repo on DO or similar should not be too big of an issue either.
For a solo dev, running a remote is a great idea and way cheaper than paying for GH private repos. You're giving up some availability and disaster recovery, but as a solo dev those aren't big problems (spin up a new host, configure your SSH keys, push). I did this years ago! When the remote is shared (with other devs or tools), then you have the hassle of provisioning accounts, updating keys when they get lost, imple…
I have always seen GitHub as the social Git. Of course I use Gitea for personal & private projects, but if you want visibility and gain from network effect, GitHub is where you needed to be. With this MS acquisition, that proposition is starting to become a problem and an uncool dependancy on MS.
Earlier quoted context omitted.
Sending patches to mailing lists is a popular way of working that is well supported by git.
Playing the devil's advocate: then you still need somewhere that people can get the current repository state from. This place might not need to do anything with pull requests or any other write action on the repository, but somewhere to clone from is necessary. This would then be the "hosted" repo, and the patches sent via mail are just that, patches.