5 ms·
Gitea Private, Fast, Reliable DevOps Platform
- fishgoesblub 1y agoI'm a big fan of Gitea. Incredibly easy to setup with Docker and is fast. As a user, it's incredible the difference in responsiveness in a GitLab instance, and a Gitea instance.
- techknowlogick 1y agoThanks so much for saying so. Not sure if you are on the latest major release yet, but hopefully you've seen that resource usage is much lower and response times are even faster.
- fishgoesblub 1y agoI am! I have my container auto-update so I'm always up to date :) I personally haven't seen decreased response times, though that's likely because my personal instance was already around 30-60ms to generate the page, pretty darn quick regardless!
- gtirloni 1y agoAnything new about it?
- techknowlogick 1y agoWe are shipping ~300 PRs monthly (plus more getting reviewed), so there are always new things :) I have a few big PRs for longstanding feature requests that should go in soon that I'm pretty excited for. edit: Im also pretty excited about the anti-crawler enhancements that went in the latest major release
- siwatanejo 1y agoDoes it support GithubActions?
- techknowlogick 1y agoIt does :) Gitea Actions are compatible with GitHub Actions. For the most part the same workflows you'd use on GitHub will work with Gitea.
- siwatanejo 1y agoCool! And does GiteaCloud have macOS&Windows agents?
- techknowlogick 1y agoNot yet, but it is something that is being worked on.
- techknowlogick 1y agoHey, I'm a part of the Gitea project leadership. Thanks for sharing. If you have any questions, please don't hesitate to ask :)
- thrill 1y agoDo you know if there are (settable) limits on image sizes using it as a container repository? Some of my larger images never fully get uploaded.
- techknowlogick 1y agoYes there are :) You can use the Package limit setting to change it (search the config docs for `LIMIT_SIZE_CONTAINER`), by default there is no limit, but if you are running into a 413 due to container uploads being so large, then it could be a reverse proxy configuration you might be running into.
- weitendorf 1y agoHow do you feel about other companies potentially also hosting gitea for third parties? Also, I’m curious about xorm and how you guys are using your internal database. Is it atypical to perform database operations outside of gitea or integrate with eg a third party users table?
- mikl 1y agoThere’s also a more community-driven/open source fork of Gitea, called Forgejo: https://forgejo.org/ https://forgejo.org/
- techknowlogick 1y agoThe Gitea project is still community-driven and has the same yearly elections for leadership that has been around for close to a decade now :) edit: Gitea is fully MIT and per our governance charter that cannot change
- tgmatt 1y agoThis is nice in theory, but what happens when a community member wants to implement SAML for the community edition, or other premium features?
- gchamonlive 1y agoIs MIT license and SSO features mutually exclusive? Or is it just a business model to sweep such features under a paid subscription?
- tough 1y agohas nothing to do with licensing and ´everything to do with business model
- techknowlogick 1y agoI'm not sure what you mean, as Gitea has SSO using many different ways, such as LDAP, OAuth2/OIDC, OpenID, SMTP, and more.
- gchamonlive 1y agoI was responding to: > what happens when a community member wants to implement SAML for the community edition It's surely just business model, but I was intrigued and thought that maybe there were some kind of incompatible licensing in popular libraries people use for these so-called "premium features"
- vunderba 1y agoLove Gitea. Took less than an hour to get an dockerized instance of it running on my Debian VPS to handle syncing my Obsidian notes between smartphone, laptop, etc.
- techknowlogick 1y agoThanks so much for saying so :) If you ever need any help please don't hesitate to hop into our forum, chat or issues tracker
- tombert 1y agoI ran this on my server for awhile. I liked it, it was pretty cool and seemed to be pretty comparable to Github, but I ended up just moving back to Github since I didn't really want to run my own infrastructure for a git repo. Still, I would definitely consider it if I were running a company; if nothing else it wouldn't be scanned by Microsoft for training.
- techknowlogick 1y agoThanks :)
- mappu 1y agoMy personal VPS was recently inundated with 800GB/month of traffic from AI scraper bots. Upon a bit of investigation they were getting stuck in some deep git history pages. I looked into Anubis and the like, but making carveouts for API endpoints seemed complicated. Luckily the Gitea devs had recently implemented `REQUIRE_SIGNIN_VIEW = expensive` as a fix. It was minimally invasive for regular users, most pages can still be accessed without login, and it completely solved the AI bot problem, my traffic and load averages are back to normal. Thank you Gitea devs for a great product, happy user for over a decade both personally and professionally.
- techknowlogick 1y agoThank YOU for using it :)
- rnhmjoj 1y agoI didn't know about this option, thanks. I had the same issue and solved it the hard way: I blackholed IP addresses from a bunch of ASNs (openai, microsoft, mistral).
- captn3m0 1y agoHad similar problems, but ended up migrating to rgit + gickup instead.
- ggandhi 1y agoLove this products and its simplicity. It was challenge to setup actions but other than that, its a perfect product for our small team.
- reactordev 1y agoGitea server uptime: 6 years, 2 months, 12 days, 3 hours, and 42 minutes. Keep making an amazing product for us who want to self-host.
- msgodel 1y agoMy solution for this is a ~20 line shell script that gets run from a checked out copy of the repo under /var/www/html and uses inotifywatch on the origin repo (pushed via ssh) to update an HTML file with a tree view and links to all the files in master as well as a second HTML file with per-branch diffs from master. Then it runs "build.sh" and archives the output. IMO this covers pretty much all the bases, it just doesn't have a flashy GUI. There's way less to configure though and one of the worst ways to spend time is configuring other people's software.
- kstrauser 1y agoThat's solving a different, and far easier, problem. I'm perfectly happy setting up my Git repos on a fileserver I have to access via SSH. That's easy enough. It works fine. But it falls down when I want to share my code with my buddy, and now I have to make a user for him. Or suppose I want some code to be world-readable because it's not sensitive and I want to clone it onto VMs that I don't want to configure to SSH into my dev server. Or I want to put a sensitive repo behind some kind of authorization, and I want full read-write access to it, but I only want my pal to have read-only access. You can do all these things yourself using standard Unix tools. I've done it. It's possible, but wow, it's way more of a pain in the neck than just installing Forgejo and saying "put repo A behind authentication, make repo B publicly read-only, and grant my clumsy friend read-only access to repo B (but allow him to open a PR if he wants to make a change to it)". Those are all real-world things I want to do, and Forgejo and friends are way easier to configure correctly than Unix permissions and a handful of SSH pub keys.
- siwatanejo 1y agoThat wouldn't have a PR review system.
- infogulch 1y agoI accidentally allowed unrestricted signups on my publicly accessible gitea instance and came back 6 months later to 20,000 accounts hosting spam and malware. Oops. Cleanup required some mysql queries and the cli. Of course its important to pay careful attention to the configuration of any app, I'm just sharing the story of how I stubbed my toe on this furniture. :) My instance is mostly used for archiving / mirroring interesting repos, more so since I had a glancing brush with censorship on github: a contributor to one of my repos was banned, which means entire issues and discussions and PRs they started were vanished overnight. This person was prolific and opened a lot of issues, so my repo became a graveyard of broken references and missing threads with conclusions and plans I no longer remember. Despite the minor scale of my project, this incident was rage inducing; it felt like github rebased my master branch to remove historical commits because someone was offended. Completely inappropriate imo. For self-hosting an archival-oriented mirror, a few features would be nice: 1. Automatically mirror every repo I star on github 2. Continuously mirror issues, discussions, and PRs 3. "safe" mirroring (see #14076), so non-ff/force-push head updates have the old head tagged to preserve history
- nodesocket 1y agoDevOps platform? Seems like a bit of a stretch, more of GitHub replacement.
- 0xbadcafebee 1y ago"Get a DevOps instance" but is it web scale?
- weitendorf 1y agoRecently started using Gitea and have two main questions: What is the scoop on the schism leading to forgejo? Like, the actual reason - is it just the existence of a for profit company with partial governance over gitea or is there more of a story? And does forgejo have substantially different plans for feature development vs gitea? Secondly, how do get in contact with contributors for sponsored work? Ideally that would be the maintainers but I feel like they have a conflict of interest with anybody trying to offer gitea to third parties…
- mappu 1y ago> What is the scoop on the schism leading to forgejo? Like, the actual reason My 2c as an outside observer - It is all about sponsored work. Gitea long wanted a CI feature but from the outside, all anyone could see, was a Drone/Woodpecker integration. Codeberg started to spend a lot of time investing in this. Then one day, Lunny(? i think) appeared suddenly with a fully compliant and working Github Actions CI implementation. The development had been done under a private sponsored contract. It's great that Actions was managed to be open sourced. It's significantly better. But Codeberg really took it the wrong way and started agitating and sponsoring a fork. Nobody wants to be left in the dark. There is a huge amount of interest in Gitea (and its forks). Everyone wants this to remain MIT, and it obviously will since there's no CLA. IMO all the "gitea company" stuff is about having a better legal structure for contract work on big features like that. That contracting is happening anyway so it may as well have a good legal structure. Forgejo PR managed to twist that good announcement into seeming as a conflict of interest, because the "Gitea" name was reused for two different concepts. Now that it's CommitGo as the (legally independent) contract development agency, it's much clearer. There is a Gitea company as well but it just needs to hold trademarks and domain names and cloud stuff. It's really a story of some great developers maturing into a more sophisticated legal and contractual level. The model is quite good, similar to e.g. Debian being the community project and Freexian being one of many commercial contractors for it. Anyways, compared to Forgejo today, Gitea has the most development activity, all of the core developers, and Forgejo have given up tracking Gitea's main branch and are now adrift. Best of luck to them. > Secondly, how do get in contact with contributors for sponsored work? CommitGo is the legal vehicle for contracting the core developers. For other contributors, bounties are managed via https://algora.io/go-gitea/home https://algora.io/go-gitea/home