From dc4320ac197813cd47b14b601c3c2f56ba462fb1 Mon Sep 17 00:00:00 2001 From: Jack Jackson Date: Sun, 5 Dec 2021 15:14:53 -0800 Subject: [PATCH] Output-capture musing in Check Your Backups --- blog/content/posts/check-your-backups.md | 1 + 1 file changed, 1 insertion(+) diff --git a/blog/content/posts/check-your-backups.md b/blog/content/posts/check-your-backups.md index 3307e12..a59e711 100644 --- a/blog/content/posts/check-your-backups.md +++ b/blog/content/posts/check-your-backups.md @@ -17,4 +17,5 @@ There's still a long way to go in improving this: * I don't have any setup instructions for my pi-hole, though that's simple enough that it shouldn't be a big problem (The Home Assistant is backed regularly backed up with [these scripts](https://github.com/scubbo/pi-tools/tree/main/hass-backup)). * The new Pi got assigned a different LAN IP, probably (I'm guessing based on limited knowledge of DHCP) because it connected to the network before I set the `hostname`. I suspect that any clients that rely on direct IP connection (i.e. those that cannot use [Avahi](https://www.avahi.org/) - which probably include Kodi clients for Jellyfin) will need to be updated. * I don't have a process set up for distributing [dotfiles](https://github.com/scubbo/dotfiles) to my Pis - in fact, I don't even have a Pi-specific `.zshrc` (I have a generic one, then specific ones for my work laptop and work desktop). +* I'd like to capture the output of all the installation components and route them to a dedicated log file, and only have my own logging output to stdout. I know I can do that on a command-by-command basis by appending `>> logfile`, but I [wonder](https://en.wikipedia.org/wiki/Ward_Cunningham#%22Cunningham's_Law%22) if there's a way to redirect output by default for an entire `.sh` file, and allow certain `echo`s to bypass that to `stdout`? * I'm reliably informed that I should be using [Kubernetes](https://kubernetes.io/) for managing containerized applications anyway ;)