title: Setting config for a chrome extension ( Configuring chrome extension parameters )
body: <p>our company wants to bundle our software (a binary .exe for windows) with a simple chrome extension (content scripts only {it does not use the chrome API}).</p>
  
  <p>Our binary .exe will dynamically generate a string which has to be passed to our chrome extension.</p>
  
  <p>My question is - how to do that?</p>
  
  <p>It seems chrome extensions lack some sort of configuration file. It would be great if I could just create an EXTENSION-ID.ini and setup the configs there or put it up on the registry (if windows).</p>
  
  <p>Alternatively, I imagine I could make my binary dynamicaly build each file of our plugin (.js, .manifest) into a separate folder setting up this string we need to pass on, and then go and package this folder into an .crx and finally set windows registry key telling chrome to install this extension on initialization. (but this does not seem like a pratical solution, and still the browser would have to be restarted to get the updated string value).</p>
  
  <p>I tried deploying an .crx and loading configurations from an external local file by making my extension inject into the page a script tag like this</p>
  
  <pre><code>&lt;script src="file://c:/path/to/configs.js"&gt;&lt;/script&gt;
  </code></pre>
  
  <p>but it didn't work, dont know why - maybe extensions can't access the file:// protocol ?</p>
  
  <p>It looks like it is possible to access the extension local path via javascript by using chrome.extension.getURL(); but that does not help either because I guess there is no easy way to insert files inside an already packaged .crx .... and if it is not already package, I mean, if it is just a folder with the files, then chrome won`t let me install the extension. Oh my...</p>