title: Best Approach for Configuration File for an Angular/RequireJS Application?
body: <p>Is there a commonly accepted best practice for maintaining a configuration file that is available on the client side (sort of an equivalent of the AppSettings section on the server side in an ASP.NET application)?</p>
  
  <p>Our application is based on Angular.  Our desire is to externalize environment-specific settings (like remote system URLs, etc) from the code itself, so that ideally an Ops person and not a developer can modify settings in one place.</p>
  
  <p>Thanks in advance for any insight!</p>