Application lifecycle with CI and Docker

- Now that we have our CI and deploy setup completed, … we can make any changes to our code … and see the whole process start automatically. … And that's the idea. … You create the initial CI, and deploy setup, … and whenever there is a commit to your code, … the rules you set in your Travis file will be implemented. … And in this case, tested with Travis, … and then deployed to Docker, … or whichever service you prefer. … So let's make a small change to the build … to see the impact and how this process works. … So right now, our build has passed, … and we our project deployed to Docker. … So let's go ahead and make a change. … So let's say, for example, we make a change to the index, … and as opposed to do, "I love Docker," … we could do something like, "Our build will succeed." … And save this. … And basically, any changes that you commit to your report. … So any code change in your project, … Travis will automatically start and then deploy … to the service you set in your Travis file. …