| Table of Contents |
|---|
deploying DB components
configurations
...
- 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 //webServerLog onto the web server.
| Code Block |
|---|
cd /var/www/html |
...
Step 3-5 may be skipped if the files are in place and there are no changes in svn.
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
4) sudo chmod u+x //webServer/var/www/html/deploy_mad.sh
5) cd //webServer/var/www/html/
6) sudo ./deploy_mad.sh
7) Point your browser to http://eas.sfgov.org/.
You should see an incomplete download because the minified javascript files missing.
Now point your browser to http://eas.sfgov.org/build.
Again point your browser to http://eas.sfgov.org/ and everything should be fine.
Remember you may have to flush your browsers cache / force the download.
<
All the above steps are much too complicated and we plan to automate it.
http://code.google.com/p/eas/issues/detail?id=327&q=deploy
>
...
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.
...
1) log onto the target geoserver node
2) run the following:
| Code Block |
|---|
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 |