Hi AI, You can implement this using Grunt.JS(Build system for Javascript framework) where you can create a development and deployed tasks separately, then create config in angularJS for dev having external resources and deployment config respectively. For Grunt and Project Scaffolding refer this(https://github.com/ngbp) and For dev and deploment automation refer this http://stackoverflow.com/questions/18476252/alternate-grunt-js-tasks-for-development-production-environments.
Happy coding, Rakshith On Sunday, January 11, 2015 at 11:22:35 PM UTC+5:30, Al J wrote: > > When I build an Angular App locally everything is fine - but when I copy > things up to production there are always little bits of things that need > changing > > for example: when developing locally I call for data against a local > source - but when in production that source changes > > How should I best encapsulate my references to external sources, how can I > get my development & deployed applications to use the proper sources > automatically > > And how should wrap all this up in an automated deployment ? > > Or to put it more succinctly: > > What is best practice for dealing with different configurations [dev, > test, prod] of your Angular webapp ? > > Thanks > > -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
