Czech/in/Japan

At the end of the previous article, I briefly hinted at various intricacies of provisioning a TLS certificate for your CloudFront distribution. Let’s briefly have a look at what you can expect and how to deal with it!

In this new short series of articles, I want to share Terraform recipes to common tasks. These will be highly opinionated (as everything on this site is), but I believe that these are fairly close to the ideal approach.

This short article loosely follows my previous adventures in self-hosting services such as mail server, file server and document server; this time, I’ll show you how I handled server monitoring and alerting so that no matter what happens to the server, I can be quickly alerted.

In my previous article, I briefly described how I modernized the way this website is hosted, and how I better utilized the VPS it’s running on. Since then, I tweaked a few things and added one really big feature. Let me show you around a bit, I think you’ll like it.

For over a year, this website operated in a fairly simple way: a lonely Digital Ocean’s Droplet was running a MySQL database and a Ghost CMS instance behind a Nginx webserver. Over the past few weeks, I decided to pimp the server up just a little bit.

Google, back in the day, used to be one of those companies that were loved by everyone and could essentially do no wrong. Due to Google’s actions in the past few years, it feels like that illusion is slowly disappearing and the true nature of the company starts showing – and it's not a nice look.

In the first article on this site, I described a way to host your site or blog on GitHub Pages while having it accessible via your own domain. I left the article with one thing left unsolved: the site was not accessible via HTTPS, and something like that would not fly in current year.

And not just host, but also set your site up to work on a custom domain and automate deployment using Travis CI. Automatic spell and grammar check included!