This is a long time coming post that I’ve kept postponing (pun intended) for ages. I enjoy browsing The Setup and I always longed for an easy way to share the way I do my computing with friends, besides linking them my dotfiles. This blog post is supposed to fill that void. A lot of this info is already documented in my private Emacs wiki, this is a more lengthy representation of it.
A bit over two years ago I blogged about migrating to Octopress from Wordpress, this time I’ll blog about migrating to Hugo from Octopress. I started messing around with Hugo because I was experimenting with Go and wanted to take a look at a simple and complete Go project. I ended up liking the simplicity of setting up a new site and decided to try porting my blog to it. I really liked the original Octopress theme and I’ve done a number of modifications to it.
Yeap, this is another rant on the security practices of Docker users. Like we didn’t have enough of those already. I recently revamped the CI system we use at my workplace. I ended up using a combination of Phabricator, Jenkins, Docker and the Docker registry, but more on this on another blogpost. Since I made heavy use of Docker for all of the above, I started poking around the Dockerfiles that are used to create the ‘official’ Docker images for a bunch of projects.
Following the example of GKH and others, I’ve added one more piece of software on my email setup and workflow. That piece is msmtp, a very simple and lightweight SMTP client, that integrates really well with the rest of my setup. At its core, msmtp does one thing. It gets mail from a MUA -in my case mutt- and relays it to a remote SMTP server. Its strength lies in its configuration file.
Note: this is a rant on how people use git. When I was introduced to git, I was told I should read this great post on git commit messages by Tim Pope. Ever since, I’ve been trying to follow that system in all of my commits across all projects. Yesterday, I decided to switch from awesome to dwm. I tried to apply one of the available dwm patches, only to notice it doesn’t work with the latest version of dwm.
In one of my previous posts, I explained my email setup in detail. Since then I’ve added one more piece of software on the “stack”. It’s called NotMuch and it’s an email indexer. After email is saved locally, thanks to offlineimap, it gets indexed by NotMuch in order to be searchable. NotMuch supports tags, uses Xapian for searches which means it supports stemming and is super quick and lightweight. I’ve integrated mutt with NotMuch using the notmuch-mutt package on Debian, mutt-notmuch-py (although this can be done in many - simpler - ways) and a couple of lines on my .muttrc.
Wanting to have more control over my email, I decided to setup my own mail server. I thought I had a pretty good understanding of how mail works, considering my mutt/offlineimap/imapfilter setup, but I must say I was pleasantly surprised while setting everything up. For my setup I decided to go with a typical postfix/dovecot installation. I used a Debian KVM machine from Prometeus, which is based in Italy and, as far as I understand, is under the Italian jurisdiction, with 512MB RAM and a 25GB SSD which ought to be enough for my needs.