What are the benefits and use cases for hosting your own over just using github/gitlab/bitbucket even google cloud and aws offer options too?
Gitea: Open source, self-hosted GitHub alternative
91–100 of 241 posts
Re: Gitea: Open source, self-hosted GitHub alternative
#92devops 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…
> 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, docker run away.
Only thing I haven't solved with this is HA but you can use a central NFS mountpoint with an HA'd setup there, and simply start a new container on another machine with the NFS mount... will require manual intervention, yes, but it's more efficient than trying to break up the dozens of moving parts.
Re: Gitea: Open source, self-hosted GitHub alternative
#93Earlier quoted context omitted.
Maybe this is the case because free projects not backed by a company can't pay a professional frontend engineer :)
Is it harder to pay a professional frontend engineer than to pay anyone else?
At least for Gogs and Gitea nobody gets payed at all, same for lots of other opensource projects. So of course it's hard to pay some frontend engineer if none contributes to the project :)
Re: Gitea: Open source, self-hosted GitHub alternative
#94What are the benefits and use cases for hosting your own over just using github/gitlab/bitbucket even google cloud and aws offer options too?
There are enough people and companies that don't trust these american companies, or they are forced to keep code within there network... Not everybody wants to give his stuff into the hands of others ;)
Re: Gitea: Open source, self-hosted GitHub alternative
#95Quick comparison from GitHub stats and READMEs: Gogs: 24,564 stars, 602 issues, has a features list. https://github.com/gogits/gogs Gitea: 5,971 stars, 733 issues, doesn't have a features list. https://github.com/go-gitea/gitea Gogs features (from README): Activity timeline SSH and HTTP/HTTPS protocols SMTP/LDAP/Reverse proxy authentication Reverse proxy with sub-path Account/Organization/Repository management Add/Re…
> Are users expected to install and find out?
When I was looking into switching from Gogs to Gitea, that is exactly what they expected you to do. I recall there being an issue saying that they won't compare the two because it's hard to keep up-to-date.
Which is a stupid excuse, considering it's supposed to be a community-based fork instead of run by one person.
Re: Gitea: Open source, self-hosted GitHub alternative
#96I've been using Gitea, previously using Gogs, for a team of 45 and have had a very pleasant experience. Getting it up and running with docker* was smooth and it works easily with Certbot. Definitely a great option for a GitHub alternative where you aren't looking for a feature-packed, i.e. large, deployment like Gitlab. It's simple and clearly delineated in its functionality. However, it does suffer from a lack of go…
Please provide constructive feedback on the docs issue tracker, or even better create pull requests to improve the documentation.
Everything including the website, documentation, blog, Hugo theme and so on is public available and also opensource.
Re: Gitea: Open source, self-hosted GitHub alternative
#97That was a painless installation. Seriously, this is something to immitate if you mean for your self-hosted application to be widely used.
If only other self-hosted/distributed projects were this easy to install. I skiped on discourse, mastodon, gitlab, etc. because they were all pain to setup on a base linux system.
Re: Gitea: Open source, self-hosted GitHub alternative
#98Earlier quoted context omitted.
Is it harder to pay a professional frontend engineer than to pay anyone else?
At least for Gogs and Gitea nobody gets payed at all, same for lots of other opensource projects. So of course it's hard to pay some frontend engineer if none contributes to the project :)
:)
Re: Gitea: Open source, self-hosted GitHub alternative
#99Earlier quoted context omitted.
> [...] and implement competent things like competent CI [...] I've got an OSX build box with a bunch of virtualbox VMs so I can build for Gnu/Linux (i386, x86_64, and arm), OSX, and Windows. Single slow box, so one runner at a time. It has to be running OSX because I haven't found any way to run an OSX VM on any other platform. I want to trigger CI on Gitlab merge requests. What does $competent_CI expand to?
> It has to be running OSX because I haven't found any way to run an OSX VM on any other platform. It is fairly easy to get decent OS X virtualization using Debian as base OS and QEMU-KVM for virtualization. You won't have niceties such as GPU acceleration but it will work. Search for "OSX KVM" on Google, it will take you where you want - unfortunately a direct link would expose me to legal liabilities. Also, be warn…
Have you figured out a way to bootstrap it without a Mac? I successfully got an image running under Vbox on Fedora, but I had to build the image first on a Mac and then export it as an appliance.
Also, performance was atrocious. It was so bad as to basically make it unusable. 5 second delay before processing mouse and key events.
Re: Gitea: Open source, self-hosted GitHub alternative
#100That was a painless installation. Seriously, this is something to immitate if you mean for your self-hosted application to be widely used. If only other self-hosted/distributed projects were this easy to install. I skiped on discourse, mastodon, gitlab, etc. because they were all pain to setup on a base linux system.
Very like Gogs.
I'm not a fan of Go, but it does lead people into some right decisions, that Ruby and Python lead them away from.
Anyway, the problems start when you want to be sure it's running all the time your server is on, and on integrating it with your other web applications. Still, it's strictly better than interpreted environments.