Gitea Private, Fast, Reliable DevOps Platform

My 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.

There’s also a more community-driven/open source fork of Gitea, called Forgejo: https://forgejo.org/

Hey, I'm a part of the Gitea project leadership. Thanks for sharing. If you have any questions, please don't hesitate to ask :)

I 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.

Gitea 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.

I 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

Recently 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…

Love 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.

I'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.

Love this products and its simplicity. It was challenge to setup actions but other than that, its a perfect product for our small team.

"Get a DevOps instance"

but is it web scale?

Anything new about it?