201–210 of 241 posts
That 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.
Pleroma is a lot easier, though.
I've been running Gitea for a long while now, basically since the fork occured. It's mostly me with some other small users for course work. It's a very pleasant and lightweight alternative to Github that I can only seriously recommend to anyone considering hosting their own Git Server. Recent update even brought mentions and reactions from Github over. (Setup Github OAuth for easy onboarding)
What do you use for CI/CD?
Earlier quoted context omitted.
Outside Jupyter Notebook Gitea supports all of these plus is managed by a community team not a singular maintainer with commit access (last I checked). A good product is not defined by having a feature list.
Well, let's call it not "feature list" but "specified vision statement" and then it should have that. It should be quite clear from the main README and the main website what distinguishes this project from others. Otherwise it's quite likely that such specification doesn't exist and goals are unclear, which usually means bloated blobb of unfinished 10 million "features".
I don't think a vision statement is necessary either since I'm a fan of developing software primarly for dogfooding, fixing problems you have is probably a good way to improve the software for others.
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…
> [...] 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?
Specifically: https://github.com/kstenerud/virtual-builders/tree/master/bu...
Earlier quoted context omitted.
Well gitea/gogs also have code hosting, wikis, issue tracking, and while CI is not tightly integrated it is fairly easy to integrate. So the value has to come from something else :) GitLab has integrated chat and kanban boards so there is other cool stuff in Gitlab but it's not really any of your listed reasons. Edit: I would have to say if I were to choose GitLab the biggest reason would be the UI. The front-end jus…
What would you recommend as CI solution for gitea? I'm looking for something that's self hosted, foss and does not require an admin to set it up for every project. GitLab offers this, but I haven't found anything that competes really.
Earlier quoted context omitted.
Gogs author didn't want to incorporate proposed changes into Gogs, so a bunch of other developers forked Gogs and went on their own promoting Gitea as true open-source by spirit and blamed Gogs author for his inflexibility. I am using Gogs, becuase it has all I need (Gitea is too little added value for me)...
> Gogs author didn't want to incorporate proposed changes into Gogs, so a bunch of other developers forked Gogs This sounds like a reasonable way for forking though. I mean what is open source for if you can't go and and implement your own features if you so desire. Sounds to me like both sides are at fault.
Quick 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…
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 on the other hand was to be more of a community project with multiple maintainers and ways for active contributors to become one.
Though Gogs has more stars, and currently, I think, more related project/integrations, looking at GH stats, Gitea has more activity, PR's, commits, etc.
That made me choose Gitea over Gogs. Really content with it.. was planning on using Gitlab at first, but it would require AWS instances with double the oomph.
The documentation could be better, agree, but a search in issues or filing a Help wanted issue comes a long way.
Another good alternative to Gitea is Fossil if you're looking for a lightweight single exe SCM.
Earlier quoted context omitted.
what was amongst the 10% you thought missing?
For one thing, the ability to search (code or issues).