As 2020 seems like a good year to get stuff done that has otherwise been neglected, I finally migrated my setup off a very old DigitalOcean droplet. It had been a steady host for years, but my initial plans to migrate from Ubuntu to CentOS7 a while back were never really completed. Centos8 is the new goodness, and I must say it was mostly a real pleasure to set up via DigitalOcean.
As the various bits of official Munin documentation seems to be in a limbo state where the current stable version (2.0.x) isn’t very well handled between the old and the new site, finding a good howto on setting up Munin with FastCGI and Nginx wasn’t as easy as it should have been. There are articles (notably https://www.webfoobar.com/node/48 ) that are a bit on the overly complicated side, as it turns out, there exists a package called munin-nginx which simplifies things a lot.
If you’re like me, you spend most of your time in the terminal. On OSX that means iTerm2 for me. I won’t go into details on how many orders of magnitude better iTerm2 is than the default Terminal app, because most likely you’re already familiar with it. Update 2018, the following is not longer true, and personally I’ve switched back to stable releases of iTerm2. What you might not know is that what is considered the stableversion of iTerm, is a bit like the stable version of Debian.
Vagrant sports out of the box integration with Saltstack, which works very well with minimum effort. However under the hood the default way this integration works is via a 4000-line bash script that bootstraps Saltstack on the VM. This would all be well and good, however, even if you were to pre-install the salt-call and salt-minion binaries onto your Vagrantbox, the salt-integration uses the same bash-script to install the configuration provided in the Vagrantfile.