Chapter 10 ■ Deployment ConsiDerations
Why do we call this process Continuous Integration? Primarily because this whole cycle can be run many times a
day (continuous) and it integrates many related aspects of the build and deployment process. Putting a sophisticated
CI process in place is often a project in itself, but generally speaking, as a developer, your entry point into all this is
through the version control system. While you may not be exposed to the complexities of setting up a CI process, it
is useful to see the contrast between the simple FTP approach we discussed above and the much more involved CI
process we just touched upon.
Summary
At the beginning of this chapter, I asserted that application deployment is an increasingly complex and multi-faceted
topic. This is indeed true, but hopefully I have given you a sense that there are tools and techniques that you can use
to manage this. While we didn’t go into much detail, there are plenty of books and online resources that are dedicated
to these topics. It can seem overwhelming, even for seasoned pros, but you don’t have to use any of these techniques
if you simply don’t need them. The real trick is to keep your eye out for anything that can make your life simpler, and
learn more about it as and when you need it.
This chapter brings us to the end of this book, but it is, of course, only the start of the AngularJS learning
process. We had a brief look at JavaScript in the first chapter, and then we moved on to the more abstract topics of
MVC and high level application design. We also looked at key AngularJS topics, such as directives, filters, and the
routing system. Still, there is plenty more to learn and lots of fun to be had doing so. You will find no shortage of great
AngularJS resources online, including the very useful AngularJS developer guide on the main AngularJS website at
https://docs.AngularJS.org/guide, and my colleague Adam Freeman’s amazingly in-depth Pro Angular book
(Apress, 2014).