" I don't see a reason to add more complexity to something that is working fine for my needs" valid point though. I would do it due to: - keeping 'meantime to

" I don't see a reason to add more complexity to something that is working fine for my needs" valid point though. I would do it due to: - keeping 'meantime to recovery' low due to having my configs in git -> fast recovery - using something like ansible for your small case to have it in git (instead of a shellscript) -> backup - perhaps a jenkins pipeline with testing the config before applying it automatically -> for quality - automatisation for having fun with it, seeing what is out there besides ssh and manuel editing At the end of the day, i assume that this automatisated process is also less dependend from myself. So i'm not sure who is doing things when you are on holiday or sick. I'm now having a small k8s cluster at home. I have never had anything which allows me to have my whole setup in git so easy with autohealing, domain management and high availability.