<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Git - Tag - vo.rs</title><link>https://vo.rs/tags/git/</link><description>Git - Tag - vo.rs</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Sat, 23 May 2026 13:00:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/git/" rel="self" type="application/rss+xml"/><item><title>From GitHub to Git Home: Self-Hosting Your Repositories with Gitea</title><link>https://vo.rs/story/from-github-to-git-home-self-hosting-with-gitea/</link><description>&lt;p&gt;Git was designed to be distributed. Every clone is a full copy of the history, which means no single server is special and no company holds your project hostage. Yet somewhere along the way the world decided that &amp;ldquo;git&amp;rdquo; and &amp;ldquo;GitHub&amp;rdquo; were synonyms, and a vast amount of the world&amp;rsquo;s source code now lives on infrastructure owned by a single corporation. That is convenient right up until it is not. If you have ever wanted a home for your repositories that you fully control, that runs on a Raspberry Pi or a spare VPS, and that boots in milliseconds, Gitea is the answer. This guide gets you from nothing to a running, self-hosted git forge you can push to over SSH.&lt;/p&gt;</description><pubDate>Sat, 23 May 2026 13:00:00 +0000</pubDate></item></channel></rss>