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.

To setup Pushover.net notification in Proxmox VE, go to:
Datacenter -> Notifications -> Notification Targets -> Add -> Webhook

Set up the following fields:

Endpoint Name: pushover (or whatever you want, note the character limitation)
Method/URL: POST, https://api.pushover.net/1/messages.json
Headers: Add one set of key-value pairs:
- Content-Type -> application/json
Body:: See pushover_proxmox-notification-webhook.json file below
Secrets: Add two sets of key-value pairs:

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

Proxmox VE tips

Just some tips I gathered over time. All in one easily reachable place so I can share it wherever I want.

Please note that unless you see a shebang (#!/...) these code blocks are usually meant to be copy & pasted directly into the shell. Some of the steps will not work if you run part of them in a script and copy paste other ones as they rely on variables set before.
The { and } surrounding some scripts are meant to avoid poisoning your bash history with individual commands, etc. You can ignore them if you manually copy paste the individual commands.
I chose to write things "in the open" that way so there's still some control and things don't become a black box.

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
```

	# For Unraid 7.x / User Scripts or Terminal Commands

	# AOOSTAR-X Service Start User Script
	#!/bin/bash
	cd /mnt/cache/appdata/AOOSTAR-X-linux && (nohup ./AOOSTAR-X > aoostar.log 2>&1 & echo $! > aoostar.pid && echo "PID saved to aoostar.pid" \|\| { echo "❌ Failed to write PID file"; exit 1; })

	# AOOSTAR-X Service Stop User Script
	#!/bin/bash
	PIDFILE="/mnt/cache/appdata/AOOSTAR-X-linux/aoostar.pid"

	# -- 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": {