Hugo, Docker-Swarm, Jenkins and Sonarqube - How this blog is made(updated)
Recently, the time to change jobs came. As the basic technology stack used for CI/CD at my new workplace is significantly different from the one in the previous job, it’s back to school (and reading and learning) for me.
I like to keep my personal technology stack in line with what I use at work. It makes my job easier, and I have a playground for quickly trying out things without interfering with company resources and, if applicable, client resources.
So, here is the list of the new stack:
- Gogs as a git repository as I wouldn’t need GitLab any more because I was switching to
- Jenkins for building and releasing my software
- Sonarqube would take care of code quality
- Docker Swarm had been my new container orchestration for a while because I didn’t really need Kubernetes for running a couple of applications for mostly personal use. I manage my Docker Swarm with the excellent
- Portainer Web UI which exposes all the Docker Swarm functionality (and adds some more features)
…to be continued soon.