From local to remote

Prior to automating segments of your workflow, it is valuable to traverse the flow manually to ensure that all phases are accounted for, and to minimize variables in the process. Most developers have likely deployed source code to either local or remote Apache servers alike, and because of that I will attempt to focus my efforts on the gotchas and nuances that apply to applications written in Angular.

Up until this point, we have conducted all local development on a Node.js server, provided by running the grunt server command from within our application's root directory. To clarify any possible confusion caused by this divergence, Angular is designed to be server agnostic, and therefore can be served from almost any backend stack you like, including Apache. Because of Angular's server agnostic design, it is fully possible to develop Angular applications locally served from Apache. I encourage a local Node.js server over Apache, because the developer experience...