Guides will help you to understand things and getting things done, you haven't done before. This section will provide a collection of our guide articles.
Linux
Containers are these fancy new thingies (technical term), that are made to make our lives as developers and operators easier. Or aren't they? This article shows what a container really is and why cgroups and the Linux Kernel are an elemental part of it.
Fedora
Running Fedora comes with a new release every 6 months. Furthermore, you are having a somewhat short maintenance time of ~13 months, only. This means, that you need to upgrade your Fedora installation occasionally. Let's see how you can do this.
DevOps
Dr. Geoffrey Alexander Moore, author of "Crossing the Chasm" is often referenced, when it comes to the core/context framework. This framework was also mentioned in the popular "Unicorn Project" from Gene Kim. What is it about? What is Core Work and Context Work?
Ansible
Let's assume you have a playbook, but you want to use different values for your variables for each time you run it. For example, you want to create a new user on your machines or change the playbook behavior. This can be done, and it is very easy with Ansible Prompts.
KVM
In some past articles, we tackled KVM and libvirt as a virtualization option on Linux. But I never introduced the basics for the same. Therefore, let's have a look at KVM and libvirt on Fedora and see how you can get started.
Podman
If you want to use containers, you need to pull images from a container registry. This is the place where container images live. But, how do you run your own registry? For your local network or development purposes, this is really useful!
DevOps
"Looking for DevOps Engineer" is something you see way more often on job platforms. But, what is this about? What does it mean to do "DevOps"? Is it really all about Docker, Kubernetes, Ansible and GitLab? I can ensure you: No, it is about a cultural change.
Fedora
In the last articles we tackled virtualization, which is perfectly fine, if you want to run full-fledged virtual machines. On the other hand, you can use containers to deploy workloads very easily. So, let's have a look how we can integrate this in our home server.
Podman
It may be a surprise to you, but I am a huge fan of Podman. Recently, there is lots of development for Desktop integration, but there are also graphical tools for the browser or Command Line. If you want to manage your images and containers with in a graphical way, this article may be for you.
Bash
The customization of a prompt is very often just some "optical enhancements". Some colors here and maybe some behavior there. If you want to have additional functionality, you may want to have a look at Starship. A blazing fast prompt with lots of cool features.
Cloud-Init
If you read my blog carefully, you may know that I really like Ansible. You can manage and configure machines and APIs very easily with Ansible automation. But what if the machine is offline or needs a configuration to boot up? This is where Cloud-Init can help.
Ansible
In the previous part of this article, we had a look at Ansible Roles and how you can use them. Now, let's develop a role on our own. It's really a piece of cake.
Fedora
In the previous article, we introduced virtualization to our home server. This allows us to start virtual machines with different operating systems. The combination of libvirt, KVM and Cockpit also allows us to create virtual machines with a graphical frontend.
Fedora
Virtualization opens a wide variety of possibilities. If you want to test a new OS release or set up some special workload, a Virtual Machine can be used easily.
Container
Building your own containers is very easy and fast to learn. But very soon, you may end up with large container images and no idea how to reduce the footprint. Since you need to download and store each image, it can be useful to minimize the images, and this article will address exactly this.
Ansible
Let's do Ansible, they said. Writing simple playbooks is easy, they said. But, should one really write playbooks over and over again? Repeat yourself? Not at all, for sure. Automation is about avoiding repetition, and Ansible has some concepts to address this.