Tutorial

At its core, Ansible is a declarative system. You describe the state in which you expect your parts of the system to be in, and Ansible, via its modules, tries to get the system there. That's the reason why modules are idempotent. But how are we to approach simple shell executions?

Ansible is an agent-less configuration management system. While agent-less it's true, it still needs two things for it to operate: SSH and python. But what if on the brand new instance we only have SSH access, but no python? Is there a way to install python with Ansible?

As I mentioned in my previous article, were multiple reasons why I chose Vim over Sublime. I wanted to focus on UltiSnips, but I realized that some ground work needs to be set first. So as the title implies, we're looking today at Vim and multiple file types.

If like me you switched to Ubuntu 18.04 LTS from Ubuntu 16.04 LTS, and had a small heart attack, well this article is for you. In this article we will try to get Gnome to resemble more the Unity interface. Here's what we will achieve:

What if instead of writing insanely long commands in the terminal to find out the namespace we're working on, there would be a command for it? Let's say kubens? With bash completion? Of course.

Let's assume that during the build, you need to archive some data on a specific node. Yes, you could just rsync to it and post data, but if you already have a Jenkins agent running there, maybe there's a simpler way.

In order to do that, we will start with creating a deployment for it. Fortunately there is already a docker image, so creating the deployment is quite straightforward:

The 3rd part of our 3 part series in which we'll explore how to get started in using germanium. We'll assume the only thing you have is python and a browser, and we'll go from writing the first test, to integrating the test suite in a CI/CD system, in our case Jenkins.

The 2nd part of our 3 part series in which we'll explore how to get started in using germanium. We'll assume the only thing you have is python and a browser, and we'll go from writing the first test, to integrating the test suite in a CI/CD system, in our case Jenkins.

In GermaniumHQ we use git branches and tags for everything. From research, to development, to test, to the actual release. Why? Let me show you how this worked in case of MoPyX - the Python Reactive UI API.