<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>links.lmorchard.com - #forgejo</title>
    <link>/tags/forgejo/</link>
    <description>Recent bookmarks tagged #forgejo</description>
    <lastBuildDate>Mon, 02 Nov 2026 08:24:53 +0000</lastBuildDate>
    <item>
      <title>Forgejo – Beyond coding. We forge.</title>
      <link>https://forgejo.org/</link>
      <description>Forgejo is a self-hosted lightweight software forge.&#xA;Easy to install and low maintenance, it just does the job.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #dev #forgejo #git&lt;/p&gt;</description>
      <pubDate>Fri, 23 Oct 2026 00:15:19 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38818</guid>
      <category>dev</category>
      <category>forgejo</category>
      <category>git</category>
    </item>
    <item>
      <title>Self-hosted Forgejo Actions Runner – David Bushell – Web Dev (UK)</title>
      <link>https://dbushell.com/2025/08/15/self-hosted-forgejo-actions-runner/</link>
      <description>Did I mention GitHub is dead to me? I’m moving my code to a self-hosted Forgejo instance at git.dbushell.com. Today I added Actions.&#xA;&#xA;Forgejo Actions are a thing like GitHub Actions for “continuous integration”. Love a bit of CI! Forgejo Actions don’t work out of the box. You need to provide a “runner” which is a machine where all the action happens inside a containerised environment.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #actions #ci #forgejo #github&lt;/p&gt;</description>
      <pubDate>Tue, 05 May 2026 15:35:07 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:38518</guid>
      <category>actions</category>
      <category>ci</category>
      <category>forgejo</category>
      <category>github</category>
      <enclosure url="https://links.lmorchard.com/static/b9ee58ea4a26b8203739b56bcfefa710.png" type="image/png"></enclosure>
    </item>
    <item>
      <title>My self-hosted Forgejo runner setup | I do what I can</title>
      <link>https://mteixeira.wordpress.com/2025/02/03/my-self-hosted-forgejo-runner-setup/</link>
      <description>In this (very long post) I will be demonstrating how I have setup my self-hosted Forgejo runners at home using Docker Compose, Docker-in-Docker and a bonus LXC. To demonstrate with a practical example, I will be building an Ansible Execution environment, to be used in my home lab automation. There will be two versions of it: a single node, and a dual node build. Both will result in the images for two platforms/architectures (AMD64 and ARM64).&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #forgejo #git #github #selfhosting&lt;/p&gt;</description>
      <pubDate>Wed, 01 Oct 2025 03:56:59 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:37768</guid>
      <category>forgejo</category>
      <category>git</category>
      <category>github</category>
      <category>selfhosting</category>
      <enclosure url="https://links.lmorchard.com/static/6302d22d64033f6e01ed5c78a8311469.png" type="image/png"></enclosure>
    </item>
  </channel>
</rss>
