homelab/.claude/projects/-home-samantha-private-Knowledge-repos-homelab/memory/feedback_ssh_scripts.md
Samantha Atkins b7c9dc81a0 cleanup
2026-04-17 20:33:17 -04:00

900 B

name description type
Use scripts on jump host instead of long SSH chains Download binaries once and distribute, write scripts to pve and run from there instead of nested SSH commands feedback

Don't run long nested SSH commands or download the same binary on every node separately. Instead:

  • Download binaries once (on pve or locally) and scp to target nodes
  • Write deployment scripts to pve and run them from there
  • Avoid the weird background task temp paths — keep things simple and visible

Why: Long nested SSH chains are fragile (env vars get lost, quoting breaks), slow, and hard to debug. Downloading the same 60MB binary 7 times is wasteful when you can download once and distribute.

How to apply: When deploying to multiple nodes, stage files and scripts on the jump host (pve), then distribute from there. Prefer simple, visible approaches over clever one-liners.