There’s something about having your own laboratory to test stuff out that appeals to me, and that’s why I decided to put together a small rack in my office. It’s cool to figure out even the most basics like “what’s the best row for this particular equipment?” and then move on from there. I have learned so many through friends and research already, and I barely started messing with this. There’s a huge community of “homelabbers” out there, of which I had no idea. Read more...

This is a reminder on how to bypass containers being unable to forward traffic internally for connections behing a private network, while also avoiding opening up FORWARD to everything – at least I assume I’m avoiding it, since I’m specifying the network (still needs proper testing, I guess), relevant iptables documentation related to it can be found on RedHat docs. Step 1. (it hangs!) trying to normally curl a container (podman) in one of my homelab’s machines: Read more...

This is an old draft from the time I worked for a company that used GCP. I have deployed two simple apps on Google’s managed version of Kubernetes, Google Kubernetes Engine. This isn’t enough for me to judge the whole thing, obviously, but I would like to write down my impressions. First of all, there is a very “simple” process. You should create your deployment manifest - which is, mostly, a file describing what your app should look like in terms of ports it’s listening to, volumes it needs, environment variables, secrets, etc. Read more...

Libs used: pytest and mock The mock lib provides a function called patch, used as a decorator to mock the things we are going to import in our to-be-tested function. In this example, CouchDB is being used and we are going to our application’s save method. Our function imports CouchDB from cloudant, but we don’t want to use the real CouchDB object. The reason is that we want to make sure all the results are coming from our program, not some third-party library. Read more...