Changes between Version 25 and Version 26 of SopUpdateBbmriApp

Timestamp:

2013-05-29T13:53:04+02:00 (12 years ago)

Author:

antonak

Comment:

--

SopUpdateBbmriApp

@@ -15 +15 @@
 2.2) If there are changes, make the migration script[[BR]]
 
-== Deploy to server ==
+'''Deploy to server'''
+
  1. As also listed here: http://www.molgenis.org/wiki/MolgenisServers the '''test server''' is at molgenis35(https://molgenis35.target.rug.nl/biobanks/) and the '''production server''' at molgenis14(https://catalogue.bbmri.nl/biobanks/) .
  1. First deploy at test server, notify [mailto:david.van.enckevort@nbic.nl david.van.enckevort AT nbic.nl]. He will notify BBMRI office, they will review the changes and if everything is ok proceed to updating bbmri production server.
@@ -21 +22 @@
    1. Ask credentials for molgenis35/molgenis14 from Pieter or Morris.
 
-=== create migration script ===
+=== create migration script according to data in live server  ===
  1. If you know the exact changes of the database, compared to the old version in live server, then the migration script is the commands that synchornize the two versions.
  1. You can compare the mysql dump files between the live and the local version. This is easier if you dump only the schemas (not the data) .
-   1. First ssh to molgenis14
-   1. create a dump file: mysqldump --no-data, -d bbmri -u molgenis –pmolgenis > ~/databaseDumps/<date>bbmriDBlive.mysql
-   1. create a local dump file:  mysqldump --no-data, -d bbmri -u molgenis –pmolgenis > ~/databaseDumps/<date>bbmriDBlocal.mysql
-   1. diff <date>bbmriDBlive.mysql <date>bbmriDBlocal.mysql
+   1. First ssh to molgenis14
+   1. create a dump file: mysqldump --no-data, -d bbmri -u molgenis –pmolgenis > ~/databaseDumps/<date>bbmriDBlive.mysql
+   1. create a local dump file:  mysqldump --no-data, -d bbmri -u molgenis –pmolgenis > ~/databaseDumps/<date>bbmriDBlocal.mysql
+   1. diff <date>bbmriDBlive.mysql <date>bbmriDBlocal.mysql
 
 === copy war file & migration script from your  computer to test server ===