<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Self-Hosting on [snowgoons.ro:~] timwa%</title>
		<link>https://snowgoons.ro/tags/self-hosting/</link>
		<description>Recent content in Self-Hosting on [snowgoons.ro:~] timwa%</description>
		<generator>Hugo</generator>
		<language>en-GB</language>
		
		
		
			<copyright>This work by Tim Walls is licensed under CC BY-NC-SA 4.0</copyright>
		
		
			<lastBuildDate>Fri, 23 Oct 2026 15:24:00 +0700</lastBuildDate>
		
			<atom:link href="https://snowgoons.ro/tags/self-hosting/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Keeping the Rust Off the Ship: An Automated Weekly Upgrade Watch</title>
				<link>https://snowgoons.ro/posts/2026-10-23-keeping-the-rust-off-the-ship/</link>
				<pubDate>Fri, 23 Oct 2026 15:24:00 +0700</pubDate>
				<guid>https://snowgoons.ro/posts/2026-10-23-keeping-the-rust-off-the-ship/</guid>
				<description>&lt;h3 id=&#34;tldr&#34;&gt;TLDR&lt;/h3&gt;&#xA;&lt;p&gt;Vulnerability discovery has gone from a trickle to a firehose. AI models are finding bugs &amp;ndash; &lt;a href=&#34;https://en.wikipedia.org/wiki/PHP2Shell&#34;&gt;PHP2Shell&lt;/a&gt; is the headline example, a class of critical unauthenticated RCEs in PHP that AI tooling surfaced in October 2026 &amp;ndash; and the &lt;a href=&#34;https://www.bleepingcomputer.com/news/security/ai-is-accelerating-vulnerability-discovery-can-defenders-keep-up/&#34;&gt;defenders are struggling to keep up&lt;/a&gt;. For a one-person infrastructure like mine, the answer is not to work faster. It is to automate the boring part.&lt;/p&gt;&#xA;&lt;p&gt;The &lt;strong&gt;Weekly Upgrade Watch&lt;/strong&gt; is an &lt;a href=&#34;https://n8n.io&#34;&gt;n8n&lt;/a&gt; workflow that runs every Monday morning. It reads the running images from my three Kubernetes clusters, checks upstream for newer releases, and hands the facts &amp;ndash; versions, dates, security advisories, reported problems, release notes &amp;ndash; to a local model (&lt;a href=&#34;https://huggingface.co/Qwen&#34;&gt;Qwen-3.8-Flash-Next&lt;/a&gt;, running through LiteLLM as &lt;code&gt;zeu&lt;/code&gt;). The model writes a short assessment for each candidate upgrade: priority, recommendation, security fixes, breaking changes, manual steps. The workflow then files or updates tickets in my &lt;a href=&#34;https://gitlab.snowgoons.ro/personal/infrastructure&#34;&gt;&lt;code&gt;personal/infrastructure&lt;/code&gt;&lt;/a&gt; GitLab project, de-duplicated against what already exists, and emails me a summary.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
