Earlier quoted context omitted.
But why? Even if you don't use kubernetes or docker images, you do wanna have it in code right? Having something like ansible would do the same thing but allows you to have your config backuped by git and allows you to recreate the env without any issues. How do you keep your mean time to recovery low? How do you document your setup? How do you automated tests if you change your config manual?
Why not? I have done this for 10+ years and it's still working flawlessly, I don't see a reason to add more complexity to something that is working fine for my needs. I don't have to change config often, maybe once a year or so.
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.