Posted April 19, 2022

And it has pretty good support for editing remote files through various protocols using TRAMP ("Transparent Remote Access, Multiple Protocols") . I think that's the normal way to run emacs, no-one's going to bother with installing their highly custom setups with dozens of packages and GUI features to run it on a server in a terminal over laggy ssh connection.
I tend to use terraform + cloudinit for most vms (we'll add some pre-build vm images to that mix on a later iteration) and everything is version controlled. On baremetal servers, I use ansible. All the code is developed on my local machine and pushed in version control.
See for an example: https://github.com/Ferlab-Ste-Justine/kvm-etcd-server
With containers, we build the image in a pipeline (we first develop them locally) and the kubernetes orchestration is gitops with fluxcd. Again, all the files and developed locally on our machines.
The age of old-school IT way of doing things where you are doing tons of stuff manually on a server is coming to an end. It is error-prone, not repeatable (and creates knowledge silos) and admittedly faster at first, but always much slower in the medium to long term.
But I'm sure at the turn of the millenium, mad emacs/vim skills were quite handy for servers setup and maintenance.
Post edited April 19, 2022 by Magnitus