title: How should I make configurable modules in AngularJS
body: <p>I've been tinkering with AngularJS and I've built up a small collection of directives and services that I would like to package into a single JS file so that I can use them anywhere.</p>
  
  <p>I have some website specific settings that my module will need for API calls and that sort of thing. I'm just wondering what the Angular way of making configurable modules is. Obviously I don't want to have to modify my reusable JS file for each website, as that kind of defeats the purpose of having it. Seeing as the values are going to remain the same for each website it seems like an awful lot of hassle to pass them in as an argument on each function call, and I'd rather stay away from global variables as much as possible.</p>
  
  <p>I've searched a lot of questions for the answers I seek, and the closest pattern I've found so far is to have my reusable module be dependant on a not included module called "settings" or something and then define that module in the page's JS file, allowing the reusable module to pull the values from it. <a href="http://codepen.io/YM_Industries/pen/bckrp">Here's an example to show what I mean.</a></p>
  
  <p>This seems backwards to me. It's kind of like having a function pull values from global values instead of passing the values in as arguments.</p>
  
  <p>Is this really the best way of doing this, or is there an alternative?</p>