title: Changing dependency paths when deploying to different directory structure than developing in
body: <p>What are some popular ways (and their caveats) of handling dependency path changes in scripted languages that will need to occur when deploying to a different directory structure?</p>
  
  <p>Let the build tool do a textual replace? (such as an Ant replace?)</p>
  
  <p>Say for example the src path in a HTML  tag would need to change, maybe also a AJAX path in a javascript file and an include in a PHP file.</p>
  
  <p><strong>Update</strong></p>
  
  <p>I've pretty much sorted out what I need.</p>
  
  <p>The only problem left is the URL that gets posted to via AJAX. At the moment this URL is in a JS config file amongst many other parameters. It is however the only parameter that changes between development, QA and production.</p>
  
  <p>Unfortunately dynamically generated URLs as @prodigitalson suggested aren't desirable here--I have to support multiple server side technologies and it would get messy.</p>
  
  <p>At the moment I'm leaning towards putting the URL parameter into its own JS file, deploying a different version of it for each of development, QA and production, additionally concatenating to the main config file when deployed.</p>