...
The DB configurations are kept here
- https://sfgovdt.jira.com/svn/DBA/eas/
I usually recommend making changes to the repo and then using svn export...
but use whatever method makes sense for you to keep things in synch.
We have yet to automate the deployment of the DB configs.
Maybe you can do this for us?
DDL, DML
DDL and DML are released using an automation framework.
Please look here
- http://code.google.com/p/eas/source/browse/trunk/etl/README
or see the developers for how this works.
web application
1) run http://code.google.com/p/eas/source/browse/trunk/releases/bin/stage_web.cmd
2) scp the output file (tar.gz) to //webServer/var/www/html/staging
3) sudo svn export https://eas.googlecode.com/svn/trunk/releases/bin/deploy_mad.sh --no-auth-cache //webServer/var/www/html/deploy_mad.sh
4) sudo svn export https://eas.googlecode.com/svn/trunk/releases/bin/set_htconf.py --no-auth-cache //webServer/var/www/html/set_htconf.py.sh
4) sudo chmod u+x //webServer/var/www/html/deploy_mad.sh
5) execute //webServer/var/www/html/deploy_mad.sh
todo - rewrite this in a single python script
deploying geoserver configurations
1) log onto the target geoserver node
2) sudo svn export https://eas.googlecode.com/svn/trunk/geoserver/deploy_geoserver.sh --no-auth-cache /usr/share/tomcat5/webapps/deploy_geoserver.sh
3) execute /usr/share/tomcat5/webapps/deploy_geoserver.sh