We do development on Tomcat and testing/production on Oracle 9iAS, release 2. To accomplish this we: 1) Store our main directory with Tomcat files in our source repository (say in $\PROJECT) 2) Store any Oracle-specific configuration info is in a separate directory WITH A DIRECTORY STRUCTURE MIRRORING #1 (say in $\ORACLE). 3) Write different ant targets for each deployment target. The Tomcat deployment just pulls code from $\PROJECT. The Oracle deployment pulls from $\PROJECT and then overwrites the files in $\PROJECT with stuff in $\ORACLE.
For example, if the web.xml file needs to be different for these two deployments then we store the tomcat web.xml in $\PROJECT\WEB-INF\web.xml and the Oracle one in $\ORACLE\WEB-INF\web.xml. Ant happily pulls web.xml from $\PROJECT and then overwrites it with the version from $\ORACLE when the appropriate target is run. This doesn't take care of other stuff like setting up datasources, but it does help. Matt ----- Original Message ----- From: "Kevin Tung" <[EMAIL PROTECTED]> To: "'Struts Users Mailing List'" <[EMAIL PROTECTED]> Sent: Thursday, September 25, 2003 10:34 AM Subject: [OT] Application Config Mgmt > How does everyone manage different deployment configurations? > > Let's say your webapp needs to run in various environments.. for example > dev, staging and production. Each environment has its own database > connection info and third party SOAP endpoints.. etc. > > What is a good way to automate (at least partly) the management of these > configurations so that.. > > * The process of promoting code from dev to staging/production will trigger > a correct change of configuration info. > * The configuration info can be stored in a code repository for history > logging and accountability. > > I've been doing this mostly manually, but there has to be a better way.. I > would love to hear about your approaches. > > Kevin > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
