This page should be a comprehensive guide to releasing a geodashboard project.
sudo /home/geodashboard/update-geodashboard.sh --force |
git clone ssh://git@opensource.ncsa.illinois.edu:7999/geod/geodashboard-v3.git cd geodashboard-v3 checkout <project specific branch name> yarn install yarn run build |
Copy the contents of the build directory of the system's proxy server
more /etc/nginx/sites-enabled/<site> | grep root |
this returns the path to the nginx root directory
cp -r gd3 gd3_backup |
sudo /home/clowder/update-clowder.sh --force |
TEST THE SITE!!!
On the database server:
sudo -u postgres pg_dump <geostream db name > geostream-backup.sql |
If not sure of the geostream database name, on the clowder server:
more /home/clowder/clowder/custom/custom.conf | grep postgres.db |
Make sure the cache is updated. If not sure run (this will take a while depending upon how much data there is):
<host>/clowder/api/geostreams/cache |
Production - Branches and Servers (after thoroughly testing dev)
All software on production branches need to be updated manually on geodashboard server
sudo /home/geodashboard/update-geodashboard.sh --force |
On clowder server
sudo /home/clowder/update-clowder.sh --force |
Production - Data
backup development and production databases
sudo -u postgres pg_dump geostream_dev > geostream_dev_$(date +"%Y-%m-%d").sql # took 42 minutes to create 6.8G db sudo -u postgres pg_dump geostream > geostream_$(date +"%Y-%m-%d").sql # took 52 minutes to create 9.5G db |
delete the production database
Stop clowder on production machine and:
sudo -u postgres dropdb geostream |
Copy dev database to production
Stop clowder on dev machine and
sudo -u postgres psql -c "create database geostream with template geostream_dev" |
Restart both clowder instances
You may also want to use visual panels to communicate related information, tips or things users need to be aware of. |
Related articles appear here based on the labels you select. Click to edit the macro and add or change labels.
|