Git is the most popular version control system in the world. A version control system records the changes made to our code over time in a special database called repository. We can look at our project history and see who has made what changes when and why. And if we screw something up we can easily revert our project back to an earlier state.

At some point when you are using docker you are going to find yourself needing to worry about container networks. Sometimes what has happened to me at least in the past is I will go ahead and create some containers based on images but for whatever reasons sometimes these containers are not on the same docker network.

I want to answer for you guys today is what is a lamp stack so we've gotten some questions and comments in the past we've had people approach us and they say hey i hear this referenced all the time i have absolutely no idea what a lamp stack is this is not something i'm familiar with and so

Today we are going to deep dive into that jenkins is and how it improves your devops continuous integration environments. We are going to cover what life is like before using jenkins and the issues that jenkins specifically addresses. Then we will get into what jenkins is about and how it applies to continuous integration and the other continuous integration tools that you need in your devops team.

If you are familiar with Jenkins, you would usually create new jobs or builds and configure them. Basically what Jenkins file is that instead of you creating and configuring jobs on the Jenkins user interface you would write a file or you would script that build and it's configuration in a file.

In this post we are going to see the docker exec and how we use it. Then we are going to see is docker attach and how we use it. So what is docker attach and how is it different from docker exec.

Email validation is a very debatted question. The one we are going to see in this post will probably not catch every single email. There’s a lot of debate for what is the best regular expression for an email and I’ve done a fairly simple one here it captures a most of them to be honest in my opinion but it’s maybe not the perfect one.

How do I run a docker container with a specific user. You connect to the terminal as root user, but I would like to connect as a different user. How can you achieve that ? The solution is to add a user flag to your command line when you start the container or in your docker compose.