Content Comparison

deploying DB components

...

configurations

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 httpsLog onto the web server.

cd /var/www/html
sudo ./deploy_eas_init.sh

If you are deploying to PROD, do not forget to repeat all of the above on the SD web server.

deploying geoserver configurations

1) log onto the target geoserver node
2) run the following:

cd /usr/share/apache-tomcat-7.0.30/webapps
sudo svn export http://eas.googlecode.com/svn/trunk/

...

geoserver/

...

deploy_geoserver_init.sh
sudo dos2unix deploy_geoserver_init.sh
sudo ./deploy_geoserver_init.sh