Installer Automated Upgrade

From OrangeHRM

Automated Upgrader

Implementation

• User needs to have a directory called "newversion" under his root folder of OrangeHRM.
• User uploads new version files to /newversion/.
  • Once uploaded, upgrader can access database information of current installation at ../lib/confs/Config.php
• Then he has to call the "upgrade" directory in it at web browser to start the upgrader (Eg: http://www.example.com/orangehrm/newversion/upgrade/)
  • Home page of the upgrader would be a login page that accept only HR Admins.
• If login details are correct, upgrader will check current version and see whether upgrading is possible.
  • If possible, user can proceed with upgrader.
  • If not, he is informed that upgrading is not possible and relevant information (from which versions to which versions upgrades are possible etc)
• In the next step, upgrader will check existing database for any data incompatibilities.
  • If found, user is asked to correct them and re-run the upgrader.
  • If not upgrader will proceed to next step.
• User is asked to provide a new database for new version.
  • This database should be authorized to the same database user as in current installation.
• Then importing data from current database to new database takes place.
  • If new database contains data fields which were not in current database, those would be filled with default values.
  • If an error occurred user is notified.
• In the next step, all necessary configuration files would be copied to new installation.
  • These would be /lib/confs/mailConf.php, /lib/confs/sysConf.php and /lib/confs/cryptokeys/key.ohrm
  • If an error occurred user is notified.
• If all above steps were successful, user would be informed successful installation.
  • After this user can login to new installation at http://www.example.com/orangehrm/newversion and verify to himself that everything has been done smoothly.
  • If user is not satisfied with new installation or find errors, all he has to do is remove "newversion" folder and corresponding database.
• To have new installation in same path as the previous one, user has to move "newversion" folder up and rename it.
  • These are manual steps that user should do via his login to web server.
    • Move "newversion" folder into same level as "orangehrm".
    • Rename "orangehrm" folder into something else (say orangehrmold).
    • Rename "newversion" folder as "orangehrm"
    • Then new installation is accessible via http://www.example.com/orangehrm/
    • User is advised to remove "orangehrmold" folder and corresponding database to avoid any duplicate or misleading issues.