Git hooks are a very handy feature in development. However, because of their local nature, configuring them from a centralized repository perspective can be challenging. In this note, I aim to find a convenient solution to this problem.
There are a lot of posts in the internet regarding which program or tool does what in Linux systems. Usually it's a brief overview of the program's functionality, a few examples, and that's it. All from the objective point of view: what we want to achieve. But there aren't so many posts discussing the algorithms in which these programs can be used. So I decided to write a quick guide you can follow to determine whether there's a problem with a server and where it is.
I love bash. A tool as trivial as command line interface (CLI, or just console) holds so many secrets, that even after 9 years of experience I still sometime find something wonderful. But today I want to talk a bit about one of my favourite tricks — aliases.
A short story about why I decided to create a personal website and blog and how I set them up and got them running. (Which turned into a manual on how to create a static website with S3 + HTTPS + custom domain name and blog for it using GitHub Pages).
How often you find yourself in the situation, when you're too bored to write a commit message? Personally, quite often. For this specific reason I finally managed to create a quick way to write commit messages.
This note is dedicated to showing how one can store CI/CD variables and secret values inside AWS Parameter Store (or Secrets Manager) and use them within Gitlab CI.
Here lies the first ever blogpost. Just so it will be here. No other particular reason.