Jekyll Originally, I had decided to locally host a Jekyll install instead of running through Github Pages. This was actually a pretty bad idea. Not only did I have the added complexity of patching the VPS, but I also had to maintain things like SSL certificates. I also had to run a reverse proxy from NGINX in order to serve SSL. This was pretty bonkers for a static content blog so I decided to go with another CMS.
Why rebuild the blog? Recently I migrated my personal blog from a self hosted Jekyll install to Pelican. I am a big fan of Pelican. Jekyll seemed to not want to be self hosted. For example, in order to serve an SSL certificate, I had to run a reverse proxy from NGINX. Similarly, I wanted to reduce unnecessary complexity. So, in the process of redesigning the blog, I decided to also reconsider hosting.
Author’s note: this was originally written by me, but then optimized by Distil Networks’ excellent marketing team. However, Distil did not publish it. I am not currently affliated with Distil Networks. GPG and Encryption At Distil, we take security and privacy very seriously. Prior to joining Distil, I did not have a very hands on understanding of GPG keys. However, we use keys extensively to ensure that there are no breaches of confidentiality.