I started blogging around 2009. Since then I used my own Wordpress instance which was customized based on my needs. I started with a managed web space which I used to run my blog. Some years later I migrated my Wordpress instance to my own hosted virtual server. Mainly to be able to also run some other projects and services next to it. Then, around two years ago, I started thinking about migrating to a containerized deployment. Unfortunately, my virtual server did not support running Containers because of its own underlying virtualization. Since then I played around with different solutions: Moving to another hosting provider, using Container as a Service or running everything on one of the available managed Kubernetes services. None of this projects ever finished – mainly due to lack of time.
In my summer vacation, I started to think about moving my blog to Medium. Mainly to finally solve my hosting issue but also to provide more ways to consume my content (using the Mobile app as a new example but also to continue supporting RSS). I finally started to migrate my content in Italy next to the pool. :) While migrating my posts I decided to split my content into two publications. One related to any kind of DevOps, Container topics. The other related to my work with IBM Connections and the ICS portfolio. I also configured to automatically posted new entries to my Wordpress as well as Medium to be sure nobody misses any content.
After migrating my content as well as using Medium I realized that my domain will get an empty space after shutting down my Wordpress instance. That’s why I decided to build an „About me“ page based on Hugo which is now being served on my domain. Providing some static information as well as contact details. But then again a question popped up: Where do I host this Hugo page? Will this break my whole idea of skipping all those admin related tasks like updating OS, software and other things? Because of this, I decided to host the website using Gitlab Pages. Gitlab Pages does not only allow me to host my static website, but it also provides me with the availability to build a fully automated pipeline which helps me to update my content as well as any code. A „git commit“ will force a build pipeline run which then checks out my content and code, builds a Docker Image and rolling out a new version without any downtime’s (I will provide some more technical details in a future post).
Those changes allowing me to only care about my content and code. Finally, last week I closed this chapter by finalizing the About me page, changing my DNS entries to the new location and shutting down my virtual server.