In a previous post, I talked about my intention to learn about Google Cloud Platform, and thanks to Globant, I had the opportunity to enroll in the GCP Partners Learning Program. Today I completed the Google Cloud Platform Fundamentals: Core Infrastructure course, the first one I did on the platform, so I wish to share with you my achievement and also some thoughts about it. It’s a great training system that takes place in Coursera, it’s seamlessly integrated with Qwiklabs, giving an interactive training experience based on video lessons and hands-on labs.
Have you ever made changes that you regretted? Git relies heavily on its history, and you may feel that your latest commit only contributes to creating a big mess in it for the other developers of the project. If you already did a commit and now you want to delete it, don’t worry, there is a solution for that. You can remove the last commit from the git history with the command below:
DockerEE is Docker’s official container platform to build and share any application seamlessly and with high-velocity being capable to use both Docker Swarm and Kubernetes as orchestrators. As it’s an enterprise-grade platform, it includes high automation, authorization, high availability, and security features. DockerEE includes the three solutions in the table below: Component Description DockerEE Docker enterprise engine including Docker Swarm and Kubernetes Docker UCP Universal Control Plane: The cluster management solution DTR Docker Trusted Registry: The image storage solution In this post, we will learn how to install all the components of DockerEE in a single virtual host for testing purposes.
Seems that I’ll work with Chef soon, so it’s time to review some lessons about it. After browsing the web for a while, I found that using Virtualbox to virtualize infrastructure and Vagrant to manage it as code is the easiest and fastest way to provision new lab environments for Chef. The first step to start working is to create a baseline, a minimal workaround built with one server host and two nodes.
Some time ago I was taking the course Master Microservices with Spring Boot and Spring Cloud but I had to leave it because these days I was getting very busy. Yesterday, after three months, I returned back and after pushing changes to GitLab repo, I noticed that changes were made with my GitHub email address instead of using the GitLab one. Last commit could be easily changed with the command below: