Build a Docker + CI environment essential for practical work all in one go!
hello. In this lecture, we covered how to set up a Docker and CI environment.
In the case of Google, Docker's influence is growing to the point where it is being used in all of its services, from Gmail to YouTube. Once you use Docker, you'll understand why its influence is growing so much. So, this is a lecture on Docker that full-stack developers or backend server developers will find incredibly helpful.
This Docker lecture starts with in-depth knowledge of how Docker works and how to use it in practice. By connecting Travis CI, Docker Hub, and AWS services, we can build a CI environment. You will learn how to use Docker in even more fancy ways.
Through this lecture, many people will learn about the current hot topic in the development field. I hope this will be an opportunity to learn more about CI systems and Docker and put them to practical use! And this lecture also connects to the Kubernetes lecture that will come out later.
This lecture is full of diagrams. Because Docker and the CI system itself are very complex. If you explain it with words, you have to visualize it separately to understand it from a standpoint of understanding. To make that part simpler , I made a diagram of all the complex parts. I tried to make it easier for those attending the lecture to understand.
Tools covered here 🧰
I use Visual Studio Code, but you can use any editor you like. I use a MAC but it works on Windows too.
Solid content, overwhelming student reviews! Also check out the <Learn Node + React by Following> series.
In short, this is the best Docker introductory course.
I haven't used Docker for over a year, but I didn't have a chance to properly learn it. I recently used it briefly while deploying a simple project and realized that it is a very useful technology. So I was thinking about learning it properly, and I found this course and took it.
I was not interested in studying development these days and was in a rut, but after taking this course, I became interested in studying development again. In particular, I only heard about CI, but when I actually tried it, I felt like I experienced a new world.
There were a lot of things to pay attention to as the course progressed, so it was a little difficult, but overall, the voice and pronunciation were good, and the explanations were just right for what I needed, so I was able to take the course comfortably.
Lastly, thank you so much for making such a great course. I'm looking forward to the Kubernetes course as well.
In my case, I didn't know much about CI before I got a job. After I got a job, I learned about CI and started studying it. I think it would be good for those who didn't know much about Docker and CI tools to learn about them. Although it's the beginning of the lecture, the teacher explained it in an easy-to-understand way with diagrams, so it was easy to understand. I'm personally making a toy project, and I'll use Docker and CI tools to build and deploy both the backend and the frontend. Thank you so much for the great lecture ^^
This was the lecture I was looking for. Other lectures are Docker A-Z, CI/CD tools A-Z, AWS A-Z, but I wanted to learn the parts necessary for practical work rather than learning one in depth and see how the CI/CD environment is run as a whole first. This lecture satisfied what I needed.
He explained it clearly and I don't know how he knew it, but he explained only the necessary parts. This is the first time I completed an Inflearn lecture :) I recommend it to those who are new to CI/CD :)
I am a junior front-end developer and I took the course because I was curious about the overall CI environment configuration. The things I liked about the course were:
1. I liked that it explained why it was necessary every time. It is good to know why it is necessary so that I can learn it and say, "Oh, that's why it's used like this," and it was good to have the appropriate explanation every time something new was introduced, which motivated me to learn.
2. I liked that the course materials were organized in diagrams. When studying development, if you don't know the overall structure, there are parts that are difficult to understand through text, but it was much easier to understand because it was explained in diagrams. You also provided PDF course materials, so I think I can refer to them when I do other projects in the future.
3. It's not easy to follow along while reviewing the lecture, but since the explanations are slightly overlapped, it was easy to learn because I was able to review them naturally.
I'll see you again in the next lecture!