Changes between Version 26 and Version 27 of SopUpdateBbmriApp


Ignore:
Timestamp:
2013-05-29T13:53:47+02:00 (11 years ago)
Author:
antonak
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SopUpdateBbmriApp

    v26 v27  
    15152.2) If there are changes, make the migration script[[BR]]
    1616
    17 '''Deploy to server'''
    18 
     17= '''Deploy to server''' =
    1918 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/) .
    2019 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.
     
    2221   1. Ask credentials for molgenis35/molgenis14 from Pieter or Morris.
    2322
    24 === create migration script according to data in live server  ===
     23=== create migration script according to data in live server ===
    2524 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.
    2625 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) .