1 min read
|
Saved February 14, 2026
|
Copied!
Do you care about this?
The author reflects on shutting down their self-hosted git server after years of operation due to overwhelming traffic from AI scrapers. They’ve redirected users to larger git hosting services like GitLab and GitHub and now only maintain a personal blog on a static site.
If you do, here's more
The author reflects on the shutdown of their self-hosted git server, which had been operational since 2011. This decision stems from persistent attacks by AI scrapers that overwhelmed the server with excessive requests, rendering it unusable. Despite previously having a public CVS server, the situation deteriorated to the point where the author chose not to rebuild the git server, leaving the management of such issues to others better equipped to handle them. Most of the repositories are now hosted on larger platforms like GitLab and GitHub, which the author has redirected users to.
The author recently updated links to point to these larger repositories, marking a significant shift in their approach to hosting. Now, only the blog and a few other minor services remain on their self-hosted setup, which uses Jekyll for static page generation. This change minimizes the risk of overload from AI scrapers, unlike the previous cgit setup. However, the scrapers still caused one outage, filling up the Apache logs with 404 responses due to the absence of the cgit service, which the bots failed to recognize. The author managed to fix the logging configuration to prevent future issues.
Questions about this article
No questions yet.