Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Gitea: Open source, self-hosted GitHub alternative

gitea.io

Post reply on HN
Print view View original

161–170 of 241 posts

Re: Gitea: Open source, self-hosted GitHub alternative

#161

Post by merb »

sytse wrote: post #140
mschuster91 wrote: post #92

Earlier quoted context omitted.

> gitlab is also so large it requires its own chef deployment to competently install it from omnibus, and has no HA roadmap in sight unless you want to break apart its rube-goldberg structure and attempt to HA the individual components of it. Use the gitlab-ce docker container and save yourself the hassle. Literally takes less than 10min to set up and a version upgrade is nothing more than docker stop, docker rm, doc…

Thanks for posting. HA is a paid feature of GitLab and will likely stay a paid feature. We're working hard on a cloud native alternative to the docker container that works well on Kubernetes. There is more information on https://gitlab.com/charts/gitlab/ and you can see the activity on https://gitlab.com/charts/gitlab/commits/master Since it is cloud native I assume it will allow autoscaling and it neatly orders ever…

> Today GitLab is using a lot of RAM and the best way to reduce that is to make the application server multithreaded https://gitlab.com/gitlab-org/gitlab-ce/issues/3592

how is multi-threading helping with memory consumption?

Re: Gitea: Open source, self-hosted GitHub alternative

#162

Post by pythonaut_16 »

tscs37 wrote: post #157
Sir_Cmpwn wrote: post #134

Earlier quoted context omitted.

An earlier comment I wrote on this subject: https://news.ycombinator.com/item?id=13297748

Gitea is however the more active (and quite active) side of the fork so I'd say it was quite successfully. You can easily check this in the contribution statistics on Github for both projects.

More active by commit active and releases.

I evaluated them both again a month ago and found that Gogs is as active or more active than Gitea by actual features developed, they just have less frequent releases.

Re: Gitea: Open source, self-hosted GitHub alternative

#163

Post by pythonaut_16 »

LeoNatan25 wrote: post #158

So this is a GitHub alternative … whose source is hosted in GitHub? Instills so much confidence.

Honestly it makes a lot of sense. Gogs/Gitea are developed and shared for people to be able to host their own Git instances.

GitHub is free for public repositories and has huge engineering teams dedicated to uptime, security, and availability.

At the very least for Gitea/Gogs to self-host the code they'd have to pay for hosting costs that GitHub is already willing to provide for free.

Re: Gitea: Open source, self-hosted GitHub alternative

#164

Post by pythonaut_16 »

striking wrote: post #32
mcny wrote: post #12

I would like to see a full-fledged docker installer something to the effect of the discourse installer that I can put on something like digital ocean or my own machine, handles https in an opinionated way (let's encrypt), and integrates with popular email services like sendgrid or mailgun (with generous free tiers).

A handful of lines added to the prescribed docker-compose file ( https://docs.gitea.io/en-us/install-with-docker/ ) and you're actually there. You would probably want to wrap it with nginx outside of docker-compose; attaching Certbot to it is thankfully very pleasant ( https://www.digitalocean.com/community/tutorials/how-to-secu... ). To integrate with SendGrid, you'd set the app.ini ( https://docs.gitea.io/en-us/con…

Check out projects like Traefik (https://github.com/containous/traefik) as well. Traefik is a reverse proxy that can automatically configure routes based on labels on your docker containers, and automatically setup Let's Encrypt certs for your subdomains.

E.g. I add a label to my Gitea container to say "Serve this from git.mydomain.com", and Traefik will start redirecting requests and automatically configure a Let's Encrypt cert.

Re: Gitea: Open source, self-hosted GitHub alternative

#166

Post by dahhowl »

Sir_Cmpwn wrote: post #134
dahhowl wrote: post #129

Earlier quoted context omitted.

Care to elaborate?

An earlier comment I wrote on this subject: https://news.ycombinator.com/item?id=13297748

The project had already forked in the past, but it eventually was deleted and was merged into the upstream because of one very simple reason: Unknwon, the creator of Gogs, came back. The fact that he left again is the main reason why the project forked again.

It's not like other people are mentioning in the thread that "some contributions would not get added" - but rather the fact that he often has really long periods of absence: just take a look at the contributions on his profile https://github.com/Unknwon

And of course, I'm not putting the blame on him - all of us need breaks from time to time - but during these periods where he can't work on the project, the project is essentially brought to a halt, seeing as there is no one else in the community of contributors who is able to merge pull requests - even if they are critical.

Re: Gitea: Open source, self-hosted GitHub alternative

#167

Post by colemickens »

pythonaut_16 wrote: post #160
sondr3 wrote: post #55

Earlier quoted context omitted.

Gitea is a fork of Gogs, so it has everything on that list and more. Sadly Gitea suffers from the usual problem that open source projects has, poor documentation. If you really want to compare feature lists, here's the one listed on their website ( https://docs.gitea.io/en-us/ ). Why compare two products by their README and not their website? Heck, why not compare them by using their test instances that are there for…

Gitea does not have every feature that Gogs has. Gitea has every feature that Gogs had at the point when they forked it, plus a few that they've ported over. But there are still features that have been in Gogs for over a year now that Gitea does not have. One example that burned me earlier this year, Gitea's backup/restore feature is still very underdeveloped. Gogs' backup/restore feature has been capable of backing…

Is there any hopes of them un-forking? I haven't followed those communities, not sure where such discussions might be happening.

Also, thanks for noting this. I had the mental perception that Gogs had really been fully surpassed by Gitea, and I need to re-evaluate now. Thanks.

Re: Gitea: Open source, self-hosted GitHub alternative

#168

Post by merlincorey »

dozzie wrote: post #144
nimbius wrote: post #39

devops sysadmin here. I started with gitlab about a year ago and can honestly say I wish I had taken gogs/gitea instead. The main problem for me is gitlabs utter dearth of somewhat counterproductive features. Git LFS support is almost a cruel joke in gitlab as git operations under the hood now take inexorably more ram to complete. In turn im rewarded with more traditional RCS programmers asking why git has problems w…

> [...] programmers asking why git has problems with their newly requested LFS and a 40gb video file they decided to store. The thing is, git, as our industry uses it, is not really a good tool for keeping artifacts , and "video" sounds like an artifact, not a source file. I'd like to see more artifact repositories, especially the ones that you can talk to from command line or from a Python/Ruby/whatever script. I ha…

What is your artifact repository called and what are the main features? I'd love to check it out.

Re: Gitea: Open source, self-hosted GitHub alternative

#169

Post by jorams »

merb wrote: post #161
sytse wrote: post #140

Earlier quoted context omitted.

Thanks for posting. HA is a paid feature of GitLab and will likely stay a paid feature. We're working hard on a cloud native alternative to the docker container that works well on Kubernetes. There is more information on https://gitlab.com/charts/gitlab/ and you can see the activity on https://gitlab.com/charts/gitlab/commits/master Since it is cloud native I assume it will allow autoscaling and it neatly orders ever…

> Today GitLab is using a lot of RAM and the best way to reduce that is to make the application server multithreaded https://gitlab.com/gitlab-org/gitlab-ce/issues/3592 how is multi-threading helping with memory consumption?

In a multi-threaded program, the threads share memory. Currently the application server is running in multiple processes, each of which contains a full copy of the core application.

Re: Gitea: Open source, self-hosted GitHub alternative

#170

Post by sytse »

merb wrote: post #161
sytse wrote: post #140

Earlier quoted context omitted.

Thanks for posting. HA is a paid feature of GitLab and will likely stay a paid feature. We're working hard on a cloud native alternative to the docker container that works well on Kubernetes. There is more information on https://gitlab.com/charts/gitlab/ and you can see the activity on https://gitlab.com/charts/gitlab/commits/master Since it is cloud native I assume it will allow autoscaling and it neatly orders ever…

> Today GitLab is using a lot of RAM and the best way to reduce that is to make the application server multithreaded https://gitlab.com/gitlab-org/gitlab-ce/issues/3592 how is multi-threading helping with memory consumption?

Because the Rails application server is currently single threaded it forks multiple processes that each take up about half a gigabyte of RAM. Running fewer processes would cause increased latency for users.
Post reply on HN