[Loris-dev] advice on updating system

[Cardillo, Garry]

Hello All,


We are currently on Loris version 14.12.1 and are planning on updating our system.  I would appreciate any insight anyone can provide.


I understand we will have to upgrade to each patch and release in order, to get up to the current release.  We have a lot of custom development in our system done by another programmer who is no longer here.  We were not using any versioning software and documentation is limited.


Referencing this page https://github.com/aces/Loris/wiki/Updating-your-LORIS:

Update your LORIS in a few steps:


  *   Download the new release codebase<https://github.com/aces/Loris/releases>. Be careful of overwriting any custom code modifications<https://github.com/aces/Loris/wiki/Code-Customization> that you may have added - you'll want to merge these with the code updates.  What is the best way to do this?  I have compared our install with the codebase for 14.12.1 and have identified all files which differ, and which are in our install only.  What is the best way to merge the code?
  *   Run composer install --no-dev and then composer dump-autoload to update dependencies and re-generate the autoload.php file  Am I simply running theses two commands on command line, or do additional steps need to be taken to update dependencies and re-generate autoload.php?
  *   Apply the MySQL release-upgrade patch found in the SQL/Release_patches<https://github.com/aces/Loris/tree/master/SQL/Release_patches> directory. Carefully note modifications to data columns and data type definitions
  *   Check your project/ directory for code that may be overriding<https://github.com/aces/Loris/wiki/Code-Customization> the main Loris codebase - these files may need updating to work with the release codebase. Note that as of 16.0 release, custom module support has changed
  *   Review all Release Notes<https://github.com/aces/Loris/releases> for every release since your last version, including minor releases -- especially those in the section specifically for Existing Projects. Follow carefully the recommended steps for existing projects

<https://github.com/aces/Loris/wiki/Updating-your-LORIS#upgrade-tips>Upgrade tips

  *   Ensure your admin user has all available permissions: INSERT IGNORE INTO `user_perm_rel` (userID, permID) SELECT DISTINCT 1, permID FROM permissions;

To preserve custom modification we have in modules, libraries and templates, would the best course of action be to create directories in /project/modules, /project/libraries, and /project/templates and copy everything to those directories?  Will that work okay with the Loris override functionality?


Also, is it correct that if we are on 14.12.1, the upgrade order would be as follows:

15.04, 15.10, 15.10.1, 15.10.2, 16.0.0, 16.0.1, 16.0.2, 16.1.0, 16.1.1, 16.1.3, 17.0.0, 17.0.1, 17.0.2, 17.0.3, 17.0.4, 17.0.5, 17.0.6, 18.0.0, 18.0.1, 18.0.2, 18.0.3, 18.0.4, 18.0.5, 19.0.0, 19.0.1, 19.0.2, 19.1, 19.1.1, 19.1.2, 20.0.0, 20.0.1?

Also, we are running everything from the same machine (mysql, php, loris, apache).  Mysql ver 14.14 distrib 5.6.35 , php ver 5.5.9, apache/2.4.7, ubuntu 14.04.  Are there any considerations that need to be taken in regards to these versions?


Thanks for any help!

Garry Cardillo
[1523292633747_image001.png]
Database Analyst/Programmer Intermediate
Department of Radiology
Functional Neuroimaging, Cognitive and Mobility Laboratory
Domino’s Farms  Lobby B Suite 1000
24 Frank Lloyd Wright Dr  PO BOX 362
Ann Arbor, MI 48106
t: 734-936-0630
f: 734-998-8403
e: cardillo at umich.edu
**********************************************************
Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.bic.mni.mcgill.ca/pipermail/loris-dev/attachments/20181023/e4af18ec/attachment.html>