Project Update - year 2021 Dec 29, 2021

The year 2021 is almost over, and I want to take a moment to describe what we achieved, how it went and what we want to do in 2021 at If you are following the project, you may have noticed, that there was not so much noise lately. But, let's first review 2021.


The very first thing I want to say is: Thank you. Thank you for reading the blog, helping with some code, following on Twitter and providing feedback in many ways. It is a pleasure to work with you and seeing the project growing.

We have done so much, that I almost lost track about the progress. Below, you can find a very small summary of some major achievements.

  • Basic infrastructure setup (based on Fedora Server and Podman)
  • different services ready like Nextcloud, Dashboard, Gitea or Minecraft
  • code provided to built your own things like a Minecraft server
  • attended many events and also provided talks
  • moved and grown SubProjects like DDOSUG
  • tons of blog articles, describing technical basics and solutions


The first core objective of is Development. We want to provide code and development work for the Open Source community. To be honest, this part was more or less successful. But let's see what happened.


One thing we want to address is the development of Ansible content. There are some minor examples, which can be found in the fedora-workstation repository, the k8s setup, some k3s automation and Nextcloud setup.


Containers should have been something, too. Unfortunately, we only addressed one new container to start our own Minecraft server. You can find the repository in our current repository. The only other container is related to our DDOSUG website, which can be found in the DDOSUG repositories.


Style-Cheat is our approach to have the design in a CSS framework. You can find the code in this repository.


Gerri has seen code, too. But was never in a shape to be released. If you want to have an idea how a Podman and KVM home server can look like, automated with Ansible, it might be interesting to check out the repository.


The second core objective of is Infrastructure.


Yep, there are a couple of nodes, that are either used for testing, storage or compute of the production environment. The migration to Kubernetes was not finalized. Nevertheless, we learned a lot about the time that must be invested to drive your own infrastructure in your free time.


We also published a couple of services. You can find a brief overview at There is the blog, code repository, Minecraft server and much more. Some of these will be canceled in 2022, since we noticed how much effort it is to keep the software updated and properly maintained. Anyway, it was a nice thing to learn for a year and we also published some articles that relate to the setup.


The third core objective of is Community. We want to connect with the Open Source community and provide value. This was done in 4 ways.


I think, the blog is one key achievement of We pushed out over 70 blog articles, reaching from Ansible to Container or Bash, Vagrant and Community events. For me, this is huuuuuuge and really want to keep up the pace. There is so much stuff in the backlog, I need at least another year to work on the topics.

In addition, we published articles for Fedora Magazine. Thank you to the Fedora folks for this huge opportunity.


In 2021, we attended and supported a couple of conferences. We gave talks at the DecompileD and Ansible Anwendertreffen, but also organized a cool conference with the DDOSUG. You can find some more detailed reports at the blog. We have already applied for even more conferences in the next year. Hopefully, we will be present at FOSDEM and CLT in 2022.

Social Media

Social Media was one thing we wanted to address. Unfortunately, this part was basically unmaintained. Aside the initial setup of some groups, nothing really happened here. But this will change. ;) Feel free to check out our social media channels at Twitter, LinkedIn and YouTube. We will provide more details in February or March how and why we will use these platforms.


The biggest community effort for me was, the setup and initialization of DDOSUG. We had one meetup per month, a YouTube channel and also organized our own conference. We also published a web page and organized a lot in social media. For me, this is a huge success, and I am happy to support and organize this together with Martin.

We have already planned more meetups for January, February and March. So, stay tuned :)


Enough of the past, let's see what we have planned for the future and how we want to address our resource limitations, so we can focus more on meaningful code for our followers, users and supporters.

Brand re-defined

The first thing is a little re-branding. The idea of was always quite clear for me, but not formulated and published in an understandable way. This will change, since we are already working on the renaming, a logo, a meaningful description and slogan and a product requirements document. We will also have properly named accounts for social media, GitHub organizations and much more.

All of this will be presented to you in January.

Core objectives re-defined

Our core objectives Development, Infrastructure, Community have seen some proper description and motivation, too. This is mostly phrasing them properly and tweaking the meaning. We also added another core objective (Open Source). Together with the re-branding, we will publish the description to you in January.

Development re-defined

As stated above, we wanted to put more focus on the development itself. Unfortunately, we underestimated the demand of running your own infrastructure.

To address these and publish more code, we will move some of our infrastructure to public services like GitHub. This also allows users to interact very easily with us and provide stories, file issues and create feature ideas.

Having the infrastructure for coding out of the way, we will have more time to publish more meaningful code to you. There are three major topics we want to address first: Container development, Ansible development and publishing our Infrastructure development.

Infrastructure re-defined

Apropos infrastructure, we will reduce and migrate our infrastructure in two ways. First, the new setup will be developed in public. You can check out the progress at any given time and follow us. Furthermore, we will design it in a way, so the setup can be used at home, for testing and production.

If we are running Kubernetes, you will be able, too. If we are running Minecraft, you will be able, too. All the code will be public in our new GitHub organization.

Community re-defined

The community work will also see improvements. Since we will migrate some work over to GitHub, Slack and other public services, it will be easier to publish blogs, releases and code snippets for you. With some improved and updated social media channels, we will also start more interaction with you. We are planning to design our roadmap together with you in polls and update you on a regular basis about the progress.

Feel free to check out our social media channels at Twitter, LinkedIn and YouTube.

In addition, we are planning to provide a completely new format to you. In February or March, you will get an official announcement, but for now: We will do a Podcast and invite tech people from all over the world to discuss products, solutions and problems in the IT industry.


Phew, that was a lot. Let me close this last article of 2021 with a huge THANK YOU! I cannot thank you enough for reading the blog, sending comments via mail, or even checking out the code.

I am thrilled to see you again in 2022 and work with you on more cool topics.


Daniel Schier

Just a guy doing stuff. Mostly #FLOSS like #Linux, #Ansible, #Podman, #k8s, #Python, #Nextcloud or whatever comes next.