<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Git on srdusr</title><link>https://srdusr.com/tags/git/</link><description>Recent content in Git on srdusr</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 03 Sep 2026 06:20:49 +0200</lastBuildDate><atom:link href="https://srdusr.com/tags/git/index.xml" rel="self" type="application/rss+xml"/><item><title>A Git Server Is Two Packages and a Location Block</title><link>https://srdusr.com/blog/a-git-server-is-two-packages/</link><pubDate>Thu, 03 Sep 2026 00:00:00 +0000</pubDate><guid>https://srdusr.com/blog/a-git-server-is-two-packages/</guid><description>&lt;p&gt;A git forge is a large piece of software. Gitea, Forgejo and GitLab all
give you issues, pull requests, accounts and CI, and all of them want
hundreds of megabytes of memory to do it.&lt;/p&gt;
&lt;p&gt;If what you want is somewhere to &lt;code&gt;git clone&lt;/code&gt; from that is not GitHub, you
need none of that. &lt;code&gt;git&lt;/code&gt; already ships a server. nginx already speaks
CGI. The whole thing is two packages and one location block.&lt;/p&gt;</description></item></channel></rss>