You’re managing your cloud infrastructure using Terraform. You’ve got your first environment up and running and you’re already reaping the benefits of a codified infrastructure. Changes are easy. But, now you need to set up a second environment (staging, prod, whatever) and you’re finding that managing this is not straight forward. There’s a bunch of arguments to remember every time you switch between environments, and your switching a lot because you want to keep them in sync. Because this is hard you tend to use auto-complete, but then sometimes you forget to change something and accidentally apply prods config to staging. Well, as in many occasions, a Makefile can probably help you there.
Along with the million other things I’ve been trying over the past year of seeking self-improvement, journaling is one of the ones I’ve had partial success with (well, more than zero-success at least). Here’s some implementation detail on my setup and how I’ve kept it as bare-bones as possible, backed-up in the cloud and, most importantly for my tin-foil fetish, secure.
This is a quick little post about how I realised that there’s a nice and easy way to view detailed information about a web certificate available to most sensible people: Firefox
This is a built-in feature of firefox: click on the little padlock icon in the address bar when visiting any website using TLS, select the view cert info and a new tab will open displaying info about the cert.
I’m planning to write a little guide on how you can host a static site effectively, but it got me thinking that first
I might wanna write about WHY you’d want to use a static site in the first place. Here goes!