<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://zackreed.me/</id><title>Zack Reed</title><subtitle>Linux, Home Servers, BASH, Photography, and Ruby on Rails.</subtitle> <updated>2026-06-04T08:10:10-04:00</updated> <author> <name>Zack Reed</name> <uri>https://zackreed.me/</uri> </author><link rel="self" type="application/atom+xml" href="https://zackreed.me/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://zackreed.me/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2026 Zack Reed </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>Wireguard fails to work on one host</title><link href="https://zackreed.me/posts/wireguard-migration-to-unifi/" rel="alternate" type="text/html" title="Wireguard fails to work on one host" /><published>2026-06-04T00:00:00-04:00</published> <updated>2026-06-04T00:00:00-04:00</updated> <id>https://zackreed.me/posts/wireguard-migration-to-unifi/</id> <content src="https://zackreed.me/posts/wireguard-migration-to-unifi/" /> <author> <name>Zack Reed</name> </author> <category term="homelab" /> <category term="vpn" /> <summary> When Docker Breaks WireGuard: A Sneaky UniFi VPN Routing Conflict Last night I decided to move my remote access VPN from a Docker hosted WireGuard instance (wg-easy) in a VM that is hosted on my Proxmox host. This VM has the bulk of my Docker containers, and it felt like it was a better idea to push the VPN access to the edge on my UniFi Fiber gateway. The migration appeared to go perfectly. ... </summary> </entry> <entry><title>Running Claude Code with a Local Model via LM Studio</title><link href="https://zackreed.me/posts/using-claude-code-with-local-model/" rel="alternate" type="text/html" title="Running Claude Code with a Local Model via LM Studio" /><published>2026-04-11T00:00:00-04:00</published> <updated>2026-04-11T20:46:51-04:00</updated> <id>https://zackreed.me/posts/using-claude-code-with-local-model/</id> <content src="https://zackreed.me/posts/using-claude-code-with-local-model/" /> <author> <name>Zack Reed</name> </author> <category term="homelab" /> <category term="ai" /> <category term="self-hosting" /> <summary> If you run a homelab and you’ve been curious about using AI coding assistants without sending your code to the cloud, this post is for you. I recently got Claude Code running against a local model through LM Studio on my MacBook Pro, and I want to walk through exactly how I set it up — including the gotchas I hit along the way. This isn’t about replacing Claude’s hosted models for serious work... </summary> </entry> <entry><title>SnapRAID 14.X and the New SnapRAID Daemon: A First Look</title><link href="https://zackreed.me/posts/snapraid-14.0-and-new-daemon/" rel="alternate" type="text/html" title="SnapRAID 14.X and the New SnapRAID Daemon: A First Look" /><published>2026-03-30T00:00:00-04:00</published> <updated>2026-06-03T17:51:46-04:00</updated> <id>https://zackreed.me/posts/snapraid-14.0-and-new-daemon/</id> <content src="https://zackreed.me/posts/snapraid-14.0-and-new-daemon/" /> <author> <name>Zack Reed</name> </author> <category term="homelab" /> <category term="snapraid" /> <category term="storage" /> <summary> If you’ve been following this blog for a while, you know SnapRAID is central to my homelab storage setup. I’ve been running it for years on top of MergerFS to protect my media array, and I even maintain a SnapRAID sync script that a lot of you have been using. So when SnapRAID 14.1 dropped alongside the brand-new SnapRAID Daemon, I had to check it out. What’s New in 14.X? SnapRAID 14.X is a s... </summary> </entry> <entry><title>Automated Docker Container Updates with Renovate, Forgejo, and Komodo</title><link href="https://zackreed.me/posts/automated-docker-updates-renovate-komodo-forgejo/" rel="alternate" type="text/html" title="Automated Docker Container Updates with Renovate, Forgejo, and Komodo" /><published>2026-03-08T00:00:00-05:00</published> <updated>2026-03-08T00:00:00-05:00</updated> <id>https://zackreed.me/posts/automated-docker-updates-renovate-komodo-forgejo/</id> <content src="https://zackreed.me/posts/automated-docker-updates-renovate-komodo-forgejo/" /> <author> <name>Zack Reed</name> </author> <category term="self-hosting" /> <category term="docker" /> <category term="homelab" /> <summary> Keeping Docker containers up to date across multiple hosts is one of those tasks that’s easy to neglect. Manual tracking doesn’t scale, and tools like Watchtower/Dockcheck that blindly pull :latest can be a recipe for unexpected breakage. A better approach is to pin every image to a specific semver tag and automate the process of opening pull requests when new versions are available. With this ... </summary> </entry> <entry><title>SnapRAID and mergerfs FAQ: Common Questions from New Linux Users</title><link href="https://zackreed.me/posts/snapraid-and-mergerfs-faq/" rel="alternate" type="text/html" title="SnapRAID and mergerfs FAQ: Common Questions from New Linux Users" /><published>2026-02-19T00:00:00-05:00</published> <updated>2026-02-19T08:43:10-05:00</updated> <id>https://zackreed.me/posts/snapraid-and-mergerfs-faq/</id> <content src="https://zackreed.me/posts/snapraid-and-mergerfs-faq/" /> <author> <name>Zack Reed</name> </author> <category term="self-hosting" /> <category term="linux" /> <category term="storage" /> <summary> Since publishing my SnapRAID and mergerfs guide, I’ve had some great conversations with readers who are new to Linux and working through their first media server setup. These are the questions that come up most often, and I wanted to compile them into one place to help others who might be wondering the same things. Table of Contents Should my parity drive be part of the mergerfs pool? Wha... </summary> </entry> </feed>
