A complete guide to set up a modern, powerful terminal environment for developers on macOS.
This guide explains how to grant the Flatpak version of Visual Studio Code access to Podman (for Dev Containers) and the KWallet keyring (for GitHub Copilot) on Bazzite KDE.
Since VS Code runs in a sandbox, it cannot directly access the host's Podman binary. We use host-spawn to bridge this gap.
A bash script to detect indicators of compromise from the SHA1-hulud npm supply chain attack.
SHA1-hulud is a supply chain attack targeting npm packages discovered in late 2025. Attackers compromise legitimate npm maintainer accounts and publish malicious versions that execute code during npm install.
Reference: https://thehackernews.com/2025/11/second-sha1-hulud-wave-affects-25000.html
| # 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" |
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).
| # -*- 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": { |
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.
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.
