You can use different settings.php files for each environment via Drupal's multisite capabilities. See <a href="http://drupal.org/node/516608">http://drupal.org/node/516608</a><br>
<br><br><div class="gmail_quote">On Thu, Mar 17, 2011 at 1:43 PM, John Fiala <span dir="ltr"><<a href="mailto:jcfiala@gmail.com">jcfiala@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">On Thu, Mar 17, 2011 at 11:40 AM, John Mitchell <<a href="mailto:mitchelljj98@gmail.com">mitchelljj98@gmail.com</a>> wrote:<br>
> For java webapps within Apache Tomcat I use a web.xml file which contains<br>
> the global variables that are specific to that server so that the production<br>
> server will have one web.xml file and the test server will have a different<br>
> web.xml file.<br>
><br>
> How can I do something similar for global variables that vary depending on<br>
> the server (i.e. production, test, demo) within Drupal?<br>
><br>
<br>
</div></div>Well, I usually put those in the setting.php files. For one thing,<br>
anything you set as $conf['blah'] in settings.php will then be the<br>
value when the code does variable_get('blah') later on.<br>
<font color="#888888"><br>
<br>
<br>
--<br>
John Fiala<br>
<a href="http://www.jcfiala.net" target="_blank">www.jcfiala.net</a><br>
</font></blockquote></div><br>