Changes between Version 30 and Version 31 of SopUpdateBbmriApp

Timestamp:

2013-05-29T14:12:20+02:00 (11 years ago)

Author:

antonak

Comment:

--

SopUpdateBbmriApp

@@ -25 +25 @@
  1. If you know the exact changes of the database, compared to the old version in live server, then the migration script is consisted of the commands that synchornize the two versions.
  1. You do not know, you can 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, create file & copy it 
+   1. First ssh to molgenis14, create file & copy it
      1. ssh molgenis@molgenis14.target.rug.nl
      1. create a dump file: mysqldump --no-data, -d bbmri -u molgenis –pmolgenis > ~/databaseDumps/<date>bbmriDBlive.mysql
@@ -32 +32 @@
    1. diff <date>bbmriDBlive.mysql <date>bbmriDBlocal.mysql
 
-=== 2.2 copy war file & migration script from your  computer to test server ===
+=== 2.2 Copy war file & migration script from your  computer to test server ===
  1. Copy the war file and the mysql migration script  from your computer  to the server as follows:
    1. scp  <filename>.war molgenis@molgenis35.target.rug.nl:./
    1. scp <migrationScriptFilename> molgenis@molgenis35.target.rug.nl:./
 
-=== 2.3 Export data from LIVE server ===
-=== 2.5 Copy data from your computer to test server ===
+=== 2.3 Copy live data from your computer to test server ===
  1. scp   ./mysql<date>LIVEdata.mysql molgenis@molgenis35.target.rug.nl:./databaseDumps/mysql<date>LIVEdata.mysql
 
-=== 2.6 Deploy at test server ===
+=== 2.4 Deploy at test server ===
  1. Ssh to the server:
    * ssh  !molgenis@molgenis35.target.rug.nl
    * You are now at /srv/molgenis/ where your files where copied.
 
-=== 2.7 Backup ===
- 1. '''BACKUP your DATABASE FIRST''':
-   * mysqldump bbmri -u molgenis –pmolgenis  > ~/databaseDumps/<date>bbmriDB.mysql
-   * Check the dumbed file if it is not just an error file …
-
-=== 2.8 Insert the data from live server to test server ===
-compare the sql file from test server with the live server. then make a migrationscript and insert this tables into testserver
-
-=== * mysql -u molgenis -pmolgenis bbmri < 29Maydump.mysql ===
-  ===
-
-=== 2.9 Apply migration steps: ===
+=== 2.5 Backup Database ===
+ 1. mysqldump bbmri -u molgenis –pmolgenis  > ~/databaseDumps/<date>bbmriDB.mysql
+ 1. Check the dumbed file if it is not just an error file …
+
+=== 2.6 Insert the data from live server to test server ===
+ * '''Insert live data (copied from your computer previously) '''
+   * mysql -u molgenis -pmolgenis bbmri < ./databaseDumps/mysql<date>LIVEdata.mysql
+
+
+
+=== 2.7 Apply migration steps: ===
  * mysql -u molgenis –pmolgenis
  * use bbmri
  * <apply mysql commands>
- * '''Backup & replace the war file on server''':
-   * The war file is in /usr/share/tomcat6/webapps/biobanks.war
-   * cp  /usr/share/tomcat6/webapps/biobanks.war ~/warFiles/<date_bbmri.war>
+
+=== '''2.8 Backup & replace the war file on server''': ===
+ * The war file is in /usr/share/tomcat6/webapps/biobanks.war
+ * BACKUP : cp  /usr/share/tomcat6/webapps/biobanks.war ~/warFiles/<date_bbmri.war>
  * Delete the old *.war  (Do NOT stop tomcat; leave it running): rm /usr/share/tomcat6/webapps/biobanks.war
  * Wait a few seconds; Tomcat will notice the *.war is gone and then it will remove the unzipped folder.
@@ -72 +71 @@
    * sudo service mysqld status
 
- * Check your deployment at: https://molgenis35.target.rug.nl/biobanks/
-
-== ''' The same steps apply to the production server molgenis14 . ''' ==
+= 3. Check your deployment  =
+=  *  Check your deployment at: https://molgenis35.target.rug.nl/biobanks/
+
+ =
+'''The same steps apply to the production server molgenis14 .'''
+
 == '''Appendix ''' ==
  * Find miscellaneous issues here: http://www.molgenis.org/wiki/DespoinaLog