Repository navigation
v1.6.0
A command given --server or --all could act on the wrong machine β install jellyfin --server rpi5 installed jellyfin here and docker restart nginx --all restarted it on every Pi β and deploy, alerts --all and a build for Windows could report a success or a reading nobody had measured; each now refuses, fails, or reads the real number.
Three things to check before upgrading. A script or MCP client config that passes --server or --all to a command that cannot use them, such as inventory or install, now gets an error instead of a local answer. --all with a command that changes a machine, such as docker restart, backup or wake, is refused; name one server with --server. And deploy and upgrade exit 1 when any server failed, which includes upgrade from a dev build. No Windows archive is published yet, so the Windows readings matter only to someone building homebutler for Windows themselves.
β οΈ Behavior changes
- Commands that cannot reach another server refuse
--serverand--allinstead of running here (#388). The two flags are global, and only the commands built to route remotely ever looked at them, soinstall jellyfin --server rpi5installed jellyfin on this machine andinventory scan --server rpi5 --jsonanswered with this machine'sserver_name.installand its subcommands,inventory,config validate,alerts init,alerts history,alerts test-notify,notify test,watch,serve,mcp,init,trust,proxmoxandversionnow exit 1 before doing anything, naming the command and the flag:install runs on this machine only; --server is not supported. A script or MCP client config that passed either flag to one of them, and got a local answer, now gets that error; drop the flag.upgrade --serveris refused too, because it upgraded every remote server while naming one;upgrade --allstill works.backup drill --all, which drills every app in one archive, is drill's own flag and is unaffected. Nothing changes for the commands that already honoured the flags, or in any JSON output --allrefuses the commands it cannot summarise (#386).docker restart,docker stop,backup,restoreandwakewith--allwere refused by the local server and sent to every SSH server, sodocker restart nginx --allrestarted it on each Pi while printing(parse error)for them.docker logs,docker topanddocker inspectwent the same way, andalerts --watch --allhung waiting on SSH servers that never answer, because a watch never returns. They now fail before any server is asked, with the list of what--allruns. Name one server with--serverinsteaddeployandupgradeexit non-zero when any server failed (#391). Both printed aβfor a server they could not reach or install on and then exited 0, so a script that deployed and went on to use the server never found out. Every server is still tried and printed, and the--jsonoutput is unchanged; the command then fails withdeploy failed on 1 of 2 servers: rpi5orupgrade failed on 1 of 3 targets: rpi5.upgradecounts the local machine as a target, soupgradefrom adevbuild, which refuses to replace itself, now exits 1. A binarydeployuploaded that then failed to run on the server was printed with aβ; it is now aβand a failureprocesses,report,docker stats,backup listandnetwork scannow answer for alocal: trueserver under--all, where it saidnot supported with --all(#386).report --alltherefore saves a snapshot on the local server too, as it already did on each SSH one;--no-savecompares without savingGET /api/portsanswers a failed read with a 500 and the reason, not a 200 with[](#384). On Windows, or on a Linux host withoutss, the dashboard's ports card said "No open ports detected" about a machine nobody had looked at. It now shows the collector's error, as the processes card already did. A successful answer is unchanged- the local server's
alerts --allreading uses thealerts:thresholds in the config, asalertsdoes, rather than a fixed 90/85/90 (#386). Thethresholdin its--json --allentry changes for anyone who set their own. Itsportsentry now names thecontainerpublishing a port, asports --jsondoes doctor --strict --allexits non-zero when any server did not pass, naming them, including one that could not be reached or read (#386).--strictis no longer sent to each server, where a warning made that server's lineremote command failedwith its JSON dumped into the errorstatusand everything built on it refuse a platform they cannot read (#384). Outside Linux, macOS and Windows,status,alerts,report,doctor,inventory, the TUI and the dashboard's status answered with 0% CPU, 0 GB of memory and no disks; they now fail withunsupported OS: <name>, the errorportsgives. No release is built for such a platform
π Fixes
--allwithout--jsonprinted(parse error)for every SSH server, because the remote was asked for text and the line was read as JSON (#386). Each server is now asked for JSON whatever the user passed, and--json --allprints the same envelope as beforealerts --allshowed alocal: trueserver at 0% CPU, memory and disk, because every answer was printed as if it werestatus, while each SSH server printed(parse error)(#386). Each command--allruns now has its own line βalertsgives the worst level and the readings beside it,docker listcounts running and stopped containers,reportcounts what needs attention and what changed β and a reading the answer did not carry is a-, never0%--all=true,--server=<name>and--config=<path>were passed on to each SSH server, which then fanned out again from its own config or looked for a server named after itself (#386). The=forms are now taken off like the spaced onesdeploy --local <path>with a path that does not exist connected to the server and could create~/.local/binthere before finding out (#391). The file is now read before the server is contactedstatusbuilt for Windows printed 0.0% CPU, 0.0 / 0.0 GB of memory, no disks and an unknown uptime, andalerts,report,doctor,inventory_scanand the dashboard passed those on as a healthy, idle machine (#384). It now reads them from Windows: memory fromGlobalMemoryStatusEx, CPU fromGetSystemTimesover the same one-second window Linux uses, uptime fromGetTickCount64, and each fixed drive fromGetDiskFreeSpaceEx, reported with its root, such asC:\, as the mount. Asubstletter is left out rather than listed as a second disk with the numbers of the drive it points into, which would also have alerted once per letter on one full disk.portsandprocessesstill refuse on Windows, as they did- a server's
key: ~\.ssh\id_ed25519passedconfig validateon Windows and then failed to load when connecting, because only~/was expanded (#384)