<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ollama on Shadowfish</title><link>https://shadowfish.night-tower.net/tags/ollama/</link><description>Recent content in Ollama on Shadowfish</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>© 2026 Creeping depths of the deep</copyright><lastBuildDate>Mon, 03 Aug 2026 11:18:00 +0200</lastBuildDate><atom:link href="https://shadowfish.night-tower.net/tags/ollama/index.xml" rel="self" type="application/rss+xml"/><item><title>Spaceballs: The Log Triage — How I Nearly Melted an Intel NUC with Vector, n8n, and Naive AI Dreams</title><link>https://shadowfish.night-tower.net/post/spaceballs-vector-n8n-log-triage-learnings/</link><pubDate>Mon, 03 Aug 2026 11:18:00 +0200</pubDate><guid>https://shadowfish.night-tower.net/post/spaceballs-vector-n8n-log-triage-learnings/</guid><description>&lt;p&gt;In &lt;a href="https://shadowfish.night-tower.net/post/n8n-sre-log-triage-auto-pr/" &gt;Part 1 of our Lazy SRE Automation series&lt;/a&gt;, we painted a glorious, utopian vision: a world where &lt;strong&gt;Vector&lt;/strong&gt; listens to container logs, &lt;strong&gt;n8n&lt;/strong&gt; orchestrates workflows, &lt;strong&gt;Ollama&lt;/strong&gt; writes code fixes, and you sleep soundly while Pull Requests open themselves.&lt;/p&gt;
&lt;p&gt;It sounded majestic on paper.&lt;/p&gt;
&lt;p&gt;Then reality hit. And by &amp;ldquo;reality,&amp;rdquo; I mean my innocent little &lt;strong&gt;Intel NUC&lt;/strong&gt; screaming in acoustic agony as its cooling fan spun at 140,000 RPM while melting into a pool of radioactive silicon.&lt;/p&gt;
&lt;p&gt;Welcome to &lt;strong&gt;Spaceballs: The Log Triage&lt;/strong&gt;. Here is everything I learned after accidentally turning my homelab into a self-inflicted Distributed Denial of Service attack.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://shadowfish.night-tower.net/post/spaceballs-vector-n8n-log-triage-learnings/featured.jpg"/></item><item><title>Lazy SRE Automation: How n8n and Ollama Write Their Own Pull Requests When Servers Crash</title><link>https://shadowfish.night-tower.net/post/n8n-sre-log-triage-auto-pr/</link><pubDate>Sat, 01 Aug 2026 20:20:00 +0200</pubDate><guid>https://shadowfish.night-tower.net/post/n8n-sre-log-triage-auto-pr/</guid><description>&lt;p&gt;Getting woken up by an alert at 2:15 AM because a container crashed on a port conflict is a rite of passage every DevOps engineer despises.&lt;/p&gt;
&lt;p&gt;Standard engineering response: Wake up, open your laptop in the dark, SSH into the host, parse &lt;code&gt;docker logs&lt;/code&gt;, realize a memory limit or port mapping is misconfigured, edit the &lt;code&gt;docker-compose.yml&lt;/code&gt;, commit the fix, and go back to sleep angry.&lt;/p&gt;
&lt;p&gt;Lazy homelab engineering response: Build an automated &lt;strong&gt;n8n + Vector + Ollama AI&lt;/strong&gt; pipeline that catches the crash log, diagnoses the root cause, writes the code patch, creates a Git branch, opens a &lt;strong&gt;Pull Request&lt;/strong&gt;, and pings your phone on Discord so you can click &amp;ldquo;Merge&amp;rdquo; without leaving bed.&lt;/p&gt;
&lt;p&gt;Here is how I built the &lt;strong&gt;SRE Log Triage &amp;amp; Auto-PR Workflow&lt;/strong&gt; using &lt;strong&gt;&lt;a href="https://n8n.io" target="_blank" rel="noreferrer"&gt;n8n&lt;/a&gt;&lt;/strong&gt;—the premier open-source workflow automation platform.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://shadowfish.night-tower.net/post/n8n-sre-log-triage-auto-pr/featured.jpg"/></item><item><title>Death to TL;DR: Fighting Unnecessary Tech Abbreviations with n8n, Ollama &amp; Discord</title><link>https://shadowfish.night-tower.net/post/death-to-tech-abbreviations-n8n-ollama/</link><pubDate>Sat, 01 Aug 2026 14:15:00 +0200</pubDate><guid>https://shadowfish.night-tower.net/post/death-to-tech-abbreviations-n8n-ollama/</guid><description>&lt;p&gt;Reading modern technical documentation has officially turned into deciphering WWII Enigma machine code.&lt;/p&gt;
&lt;p&gt;You open a blog post expecting a simple explanation of a system, and within three paragraphs you are hit with:&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;&lt;em&gt;&amp;ldquo;Our &lt;strong&gt;CI/CD&lt;/strong&gt; pipeline deploys an &lt;strong&gt;eBPF&lt;/strong&gt; probe into a &lt;strong&gt;K8s&lt;/strong&gt; pod using &lt;strong&gt;ACME TLS&lt;/strong&gt; certs stored in &lt;strong&gt;1P&lt;/strong&gt;, monitored via &lt;strong&gt;PROM&lt;/strong&gt; and logged to &lt;strong&gt;LOKI&lt;/strong&gt; (&lt;strong&gt;TL;DR&lt;/strong&gt;: it works).&amp;rdquo;&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;&lt;p&gt;Whatever happened to using actual words? When did software engineering decide that typing six extra letters was a medical emergency?&lt;/p&gt;
&lt;p&gt;I genuinely detest unnecessary tech abbreviations. And because I am a homelab engineer, I didn&amp;rsquo;t just complain about it—I built an automated &lt;strong&gt;n8n + Ollama AI Acronym Police&lt;/strong&gt; bot (building on my &lt;a href="https://shadowfish.night-tower.net/post/n8n-multi-llm-orchestration/" &gt;n8n multi-LLM orchestration setup&lt;/a&gt;) to catch abbreviations red-handed and force them to explain themselves on Discord.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://shadowfish.night-tower.net/post/death-to-tech-abbreviations-n8n-ollama/featured.jpg"/></item><item><title>Inside Night-Tower: The Over-Engineered Homelab Powered by Fighter Jets and AI Chaos</title><link>https://shadowfish.night-tower.net/post/night-tower-homelab-architecture/</link><pubDate>Sat, 01 Aug 2026 13:30:00 +0200</pubDate><guid>https://shadowfish.night-tower.net/post/night-tower-homelab-architecture/</guid><description>&lt;p&gt;Most normal human beings buy a single-bay Synology NAS, plug it into their router, copy their family photos over, and call it a day.&lt;/p&gt;
&lt;p&gt;Then there are homelab enthusiasts.&lt;/p&gt;
&lt;p&gt;We look at a simple home network and think: &lt;em&gt;&amp;ldquo;You know what this single-bedroom apartment really needs? A three-node high-availability baremetal Proxmox hypervisor cluster, enterprise-grade OPNsense firewalling, automated GitOps CI/CD pipelines, local AI LLM orchestration, and 1Password-vaulted Ansible playbooks.&amp;rdquo;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Welcome to &lt;strong&gt;Night-Tower&lt;/strong&gt;—the homelab where enterprise-grade architecture meets absurd levels of over-engineering.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://shadowfish.night-tower.net/post/night-tower-homelab-architecture/featured.jpg"/></item><item><title>Battle of the Micro-LLMs: Can a 2GB GPU Save You From CPU Agony?</title><link>https://shadowfish.night-tower.net/post/llm-token-benchmark-showdown/</link><pubDate>Tue, 28 Jul 2026 10:45:00 +0200</pubDate><guid>https://shadowfish.night-tower.net/post/llm-token-benchmark-showdown/</guid><description>We benchmarked Qwen 2.5, Gemma 2, and Ministral 3 across two homelab machines. Spoiler: Gemma 2 took 140 seconds to load on CPU, giving us time to rethink life choices.</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://shadowfish.night-tower.net/post/llm-token-benchmark-showdown/feature.jpg"/></item></channel></rss>