 In the last video, we have seen an example of how you can take your source code and deploy it onto OpenShift by using a process called source to image where we picked up a builder image which is a PHP and we put the source code together, OpenShift built an image for your application based on your source code and the build and the build image it pushed the application image into a repository that is running on this OpenShift environment and then it took that same application image Docker image and it deployed that as a part. So we have an application that has the PHP front end running as a single part and this is that part, right? This is running your application the front end and we also have a database part that is running your MySQL. So now let's look at how this whole thing comes together like as a developer you need an experience where you can make code changes frequently and you want to push those code changes into OpenShift and let OpenShift deploy those code changes seamlessly without worrying about all these things that are happening behind the scenes, right? So let's see how the entire workflow from a developer standpoint would look like in this video. First thing we'll go to builds and let's look at what is here. So the source control repository is mapping to your GitHub and then what you see here is triggers and here you will find a GitHub web hook URL. Let's copy that. Now take this web hook URL go to your source control repository and configure it there. So I'm on the GitHub for my project and I'm going to settings here and in settings I see the web hooks option and I want to add a web hook. Now I'll paste my URL here and then I want to disable SSL and I want to add the web hook. Now we have configured our GitHub repository now to push the code changes in if any or commits to this repository if any to the OpenShift environment. Now let's test that. I'm going back and let's look at the application. It looks very bland. There is no it's just displaying the users from the database. There is no formatting nothing. So let me make some small change to this DB test of PHP. I'll go to the place where it is displaying this data and I'll edit it make some small changes like I want to say the user ID I want to display this before each user ID user name for each user name and there is a mistake here. I want to fix that. I want to include a line break here. So let me commit these changes. I'll say added labels before I commit. Let me show you what we have here under the builds. You'll see there is one build that was done before right now what you'll notice is once I commit these changes an additional build will get triggered automatically. I just committed the changes. I'll come back here and see GitHub has pushed those changes to OpenShift using that web hook URL and it automatically triggered a new build here. Now this build process will happen just like before. So I can the build name is DB test 2. So I can look at the logs here and see what's going on. It has by this time it has actually built the image and it has successfully pushed that newly built image into the OpenShift's Docker registry. Once the build is complete, the part is updated with the new code changes. So if I now refresh my application, my changes are here. It's as simple as that. So to summarize what we just did, I took the web hook URL and I configured that in my source control repository and as I'm making the code changes and committing those code changes to the GitHub, which is my source control repository, using that web hook, the source control repository or this pushing the changes to OpenShift and OpenShift automatically triggers a new build and it uses the same PHP build image to complete the new build and it will push that application image into the OpenShift's Docker registry and once it is pushed, it will trigger a deploy process again and once and it will take the newer image of this application and it will deploy it onto this part and the new changes are seen here. Thanks a lot for watching.