During the dark side of quarantine, I had to keep my hands busy, and instead of writing on this blog (sorry!) I started streaming on Twitch instead. To add some interactivity with my viewers, I made my own bot to let my viewers create and display custom Images and GIFs with text… Basically, a Meme Generator! This is the story of designing it, building it in Go, and running it Heroku 🤩
I recently decided to replace my k8s home cluster with a Hashicorp Nomad cluster on my 3 Raspberry Pis. When I was using it, I found myself writing a significant amount of HCL files, and I have been missing Helm’s simplicity.
As an SRE, I have been working with Kubernetes for a while now. During this time, I had to install, configure, and distribute some apps using Helm. For me, it is a de-facto standard when it comes to deploy and maintain apps that otherwise would require a way bigger list of YAML files. Can we do the same for Nomad Jobs’s definitions?
During the last year I have learned how important it is to build, test and deploy using always the same docker container as well as reducing its size. As I have not found anything online, I want to remember and share it: I am testing my go packages with a multistage docker build inside my pipeline on GitLab. The odd way of testing go docker containers Especially when implementing CI best practices, I have seen projects running tests in different ways: