Nimbus

Yes, the heading is absolutely correct. Gitlab is moving from Microsoft Azure to Google Cloud Platform (GCP). I know what you might be thinking, but this decision wasn't made after Microsoft decided to buy Github. But, all this migration was being planned even before that. Most of the things in this article are taken from the original article of Gitlab:  Here They believe  Kubernetes  is the future. It's a technology that makes reliability at massive scale possible. This is why earlier this year they shipped native  integration with Google Kubernetes Engine  (GKE) to give GitLab users a simple way to use Kubernetes. Similarly, they've chosen GCP as their cloud provider because of their desire to run GitLab on Kubernetes. Google invented Kubernetes, and GKE has the most robust and mature Kubernetes support. Migrating to GCP is the next step in only plan to make GitLab.com ready for their mission-critical workloads. It's what they think. I think even if ...

When it comes to " dockerization " of your application, it might be possible that your apps are under continuous development and needs to generate new docker image frequently based on the app updation. So, if haven't gone through my previous Articles regarding  Docker Overview  and  Docker Basics , then please go through those first. Solution : Automation of the Docker Build using Docker Automated Build feature of hub.docker.com How? Let's find out. All we have to do is to link Docker and Github to automate the build process. Following steps will teach you to do so with a sample project on Github. Step 1 : Create account on both Github.com and hub.docker.com Step 2 : Create a repository on the Github as per your requirements. Step 3 : Create a file named as "Dockerfile" with the following contents FROM ubuntu:16.04 USER root WORKDIR /root RUN apt-get update -y \     && apt-get install -y apache2 RUN ...