You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

This page should be a comprehensive guide to releasing a geodashboard project.

Step-by-step guide to complete release for mixed v2 and v3 system

  1. Softare - Development Branches and Servers
    1. Geodashboard v2
      1. Core
        1. Geodashboard V2 is used for multiple projects
          1. release will be decided by larger group - contacts are Luigi Marini, Indira Gutierrez Polo
          2. v2 should be on the most recent version of development branch on project's development server
        2. Project specific configuration
          1. the project specific configuration develop branch should be up to date with all necessary updates
      2. Build
        1. If set up with Puppet, the development server should update automatically to the most recent build
          1. If you need to update manually, shh to the geodashboard developement server
          2. sudo /home/geodashboard/update-geodashboard.sh --force
    2. Geodashboard v3
      1. Software
        1. Each project should have a specific branch of v3 named by project name, which the master branch merged into the configuration 
          1. The master branch should be merged into the project branch which maintains it's specific configuration
      2. Build (local by user)
        1. 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

        2. Copy the contents of the build directory of the system's proxy server

          1. check the nginx root directory
          2. more /etc/nginx/sites-enabled/gltg | grep root

            1. this returns the path to the nginx root directory

          3. cd to nginx root directory
          4. there should be a directory call 'gd3' (maybe named something else)
          5. backup the directory
          6. cp -r gd3 gd3_backup
          7. copy the new build files into the gd3 directory (delete the previous of just overwrite)
    3. Clowder 
      1. clowder on dev uses the clowder development branch
      2. should update automatically 
      3. to update manually
        1. sudo /home/clowder/update-clowder.sh --force

    4. TEST THE SITE!!!

  2. Development - Data
    1. Make sure all data is up to date and correct
    2. backup the database 

      1. On the database server:

        sudo -u postgres pg_dump <geostream db name > geostream-backup.sql

      2. If not sure of the geostream database name, on the clowder server:

        more /home/clowder/clowder/custom/custom.conf | grep postgres.db

    3. 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

 



  • No labels