<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Homelab on Evan Coleman</title><link>https://edc.me/tags/homelab/</link><description>Recent content in Homelab on Evan Coleman</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 19 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://edc.me/tags/homelab/index.xml" rel="self" type="application/rss+xml"/><item><title>Introducing Leo: From OpenClaw to Native Claude Code</title><link>https://edc.me/posts/introducing-leo/</link><pubDate>Sun, 19 Apr 2026 00:00:00 +0000</pubDate><guid>https://edc.me/posts/introducing-leo/</guid><description>&lt;p>Like many, I participated in the AI agent revolution that is &lt;a href="https://github.com/openclaw/openclaw">OpenClaw&lt;/a> early this year. In the beginning, it was magical. It managed my inbox and calendar, kept me up to date on news. I even tried using it for coding.&lt;/p>
&lt;p>It wasn&amp;rsquo;t long before I started to get frustrated. OpenClaw is a genuinely impressive
project, but it moves fast and updates would frequently break things. It got to the point where I found myself spending more time making sure things were working than actually getting any benefit out of it. Eventually I found myself reaching for Claude Code more than my OpenClaw agent.&lt;/p></description></item><item><title>Self-Hosting Mastodon on Nomad</title><link>https://edc.me/posts/self-hosted-mastodon/</link><pubDate>Sat, 08 Feb 2025 12:00:00 +0000</pubDate><guid>https://edc.me/posts/self-hosted-mastodon/</guid><description>&lt;p>For a while, I’ve been running my Mastodon instance, coleman.social, on a DigitalOcean VPS. It worked fine, but as my self-hosted infrastructure matured, it made sense to move it over to my Nomad cluster. The benefits? Faster response times, better resource utilization, and lower costs. Plus, I wanted full control over my setup.&lt;/p>
&lt;h1 id="why-self-host">Why Self-Host?&lt;/h1>
&lt;ul>
&lt;li>&lt;strong>Cost Efficiency&lt;/strong> – Running Mastodon on DigitalOcean meant paying for a dedicated VPS. Now, it runs on my existing infrastructure with no extra monthly costs.&lt;/li>
&lt;li>&lt;strong>Performance&lt;/strong> – With direct access to my Synology SAN for volumes, everything runs smoother and faster.&lt;/li>
&lt;li>&lt;strong>Full Control&lt;/strong> – Instead of relying on a managed VPS, I can tweak the stack however I need, with consistent configurations across services.&lt;/li>
&lt;li>&lt;strong>Scalability&lt;/strong> – By moving to Nomad, I can easily scale up or down as needed without dealing with VPS limitations.&lt;/li>
&lt;/ul>
&lt;h1 id="infrastructure-overview">Infrastructure Overview&lt;/h1>
&lt;h2 id="nomad--consul-for-orchestration">Nomad &amp;amp; Consul for Orchestration&lt;/h2>
&lt;p>Mastodon is now managed as a Nomad job, ensuring clean deployments and automated scheduling.&lt;/p></description></item></channel></rss>