<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Github on Matt Ellis</title><link>https://matt-ellis.dev/tags/github/</link><description>Recent content in Github on Matt Ellis</description><generator>Hugo</generator><language>en-GB</language><lastBuildDate>Sun, 28 Jun 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://matt-ellis.dev/tags/github/atom.xml" rel="self" type="application/rss+xml"/><item><title>Notes on running a self-hosted GitHub Actions runner</title><link>https://matt-ellis.dev/posts/github-actions-runner/</link><pubDate>Sun, 28 Jun 2026 09:00:00 +0000</pubDate><guid>https://matt-ellis.dev/posts/github-actions-runner/</guid><description>&lt;p&gt;Self-hosted runners are one of those things that sound like pure upside until you&amp;rsquo;re three hours into debugging why a workflow that passes on GitHub-hosted runners silently fails on your own box.&lt;/p&gt;
&lt;p&gt;The economics are real though. If you&amp;rsquo;re running anything that hits the free tier limits, or if you need access to resources on your private network, a self-hosted runner pays for itself fast. Mine runs on the same Proxmox box as everything else, allocated 2 cores and 4 GB, and it handles CI for about six personal repos without breaking a sweat.&lt;/p&gt;</description></item></channel></rss>