Adam Kaminski thimslugga

No route to host on macOS Sequoia

formerly "macOS Sequoia + HomeBrew + cron = pain!"

Each year as Apple's World Wide Developer Conference (WWDC) approaches, I start to think about upgrading macOS to the version that was released at WWDC the previous year. I reckon that's a good way of minimising your pain and suffering, not to mention giving developers a chance to patch things that got broken when the API goal-posts moved.

The end of May 2025 was when I decided to upgrade both a 2019-era Intel iMac and an Apple M2 MacBook from Sonoma 14.7.1 to Sequoia 15.5.

Aside from the seven fractions of eternity that macOS updates seem to demand these days, it all seemed to go swimmingly. The only explicit grizzle was from Carbon Copy Cloner, which wanted a later version (on my to-do list).

GitHub CLI (gh) User Guide

Sync Your Shell PATH to macOS GUI Apps Manually with This Script

The Problem

Are you struggling with macOS GUI applications (like IDEs, text editors, or other tools launched from Finder or Spotlight) not finding command-line tools installed via Homebrew (/opt/homebrew/bin), MacPorts, or in custom directories like ~/bin or /usr/local/bin? This happens because GUI applications on macOS do not automatically inherit the PATH environment variable set by your login shell configuration files (like .zshenv, .zprofile, .bash_profile, or .bashrc). Your carefully configured shell PATH works in the Terminal, but GUI apps remain unaware of it.

The Solution

This Bash script provides a simple, manual way to apply the PATH from your current Terminal session to the macOS GUI environment. Instead of complex automatic synchronization, you run this script whenever you want to update the PATH that GUI applications will use.

I'll complete the text with the process management information:

This script performs DNS TXT record lookups once per minute for 24 hours straight. Each lookup uses a unique random name in the format 'delver-xxxxxxxx'.

Requirements

Python 3.x
Your computer must stay awake the entire time (disable sleep/hibernate)
Internet connection for the full 24 hours

Setting Up MCP Servers on Windows

A step-by-step guide to setting up Model Context Protocol (MCP) servers for Claude Desktop on Windows.

Prerequisites

Install Node.js (v18.x or later)
- Download from: https://nodejs.org/
- Verify installation by opening Command Prompt (CMD) and running:
```
node --version
npm --version
```

Why Virtualize

you get full backups, snapshots, a build in monitor to debug. You can also better utilize the hardware. Not every service (very few imho) are feasible to run inside HAOS

easy troubleshooting (basically a build in monitor and keyboard), snapshots to test and then potentially revert things you otherwise would be too afraid to try. The ability to backup a whole machine and run other VMs/Containers and so on

I recommend running critical/unrelated things (adguard, unifi or bitwarden for example) or those that require flexibility outside of HAOS if you can as these will go down on OS updates. You can't do that with a bare metal HAOS install.

Some of my previous answers to why run HAOS virtualized. Just some of the benefits and reasons why I recommend it.

Podman quadlet example

quadlet-exec.sh - exec macro for quadlet containers

	# -- mode: justfile --

	# ==============================================================================
	# Settings - Control Just's behavior
	# ==============================================================================

	# Set the shell used to execute recipes. Array form is recommended.
	# -u: Treat unset variables as an error.
	# -c: Read commands from string.
	set shell := ["bash", "-uc"]

	// Zed settings
	//
	// For information on how to configure Zed, see the Zed
	// documentation: https://zed.dev/docs/configuring-zed
	//
	// To see all of Zed's default settings without changing your
	// custom settings, run `zed: open default settings` from the
	// command palette
	{
	"edit_predictions": {

	{
	"HTML document": {
	"prefix": "html",
	"body": ["<!DOCTYPE html>\n<html lang=\"en\">\n<head>\n\t<meta charset=\"UTF-8\">\n\t<meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n\t<title>Document</title>\n</head>\n<body>\n$1\n</body>\n</html>", "$0"],
	"description": "HTML document"
	}
	}