In this post I will be discussing my recent move to using Jenkins for CI CD pipelines, this is the first post in this series covering my process on migrating the pipelines from the pipelines but these posts are also part of the migrating to github series.

Why?

So why Jenkins? Well simply put I wanted to know how it works better, Jenkins is one of the tools I have used professtionally a few times however each time I have another team has managed the environment, this has restricted a number of feature I’ve been exposed to, this fact has made it difficult to suggest improvements as I don’t know what is possible.

In this post I will discussing the reasons for my recent migration to github from gitlab and the initial process I took to move my repositories over to github this is a the first post in the series as I document the additional steps of using a mixture of github actions and Jenkins to build brand new pipelines with the devops knowledge I have built up.

Why?

It’s important to note throughout this series when I mention Gitlab I am specifically talking about Gitlab enterprise edition self-hosted which I was doing at no cost utilizing oracle cloud’s always free tier.

In this post I’ll be discussing how I have automated the deployment of hugo both to a development environment and production environment.

With hugo I wanted to achieve 2 things a new speedy blog and using my DevOps skills to deploy it, this is probably going to evolve in the future as I start venturing into hosting my own kubernetes cluster but the purpose of this blog is document the journey not the destination.

Here it is the new hugo site, I was on the hunt for a new faster way to deliver my blog and I stumbled across hugo, hugo is a static site generator that’s written in Go and utilizing markdown to write posts, essentially it works by writing your posts in markdown then you use hugo to generate static html files.

Because the site is just static HTML it loads incredibly fast and pairing it with cloudflare’s CDN the load on the web-server is significantly reduced, which will in the near future will be replaced with a kubernetes setup.

This is a quick guide to show you how to set up an openvpn service that automatically connect’s to PIA (Private Internet Access), the use case for this is to protect a single machine such as a laptop when using a public network or a server that runs services that need a different public IP from the rest of the network.

This guide is for educational purposes only I hold no responsibility for any issue that arise from following this guide.