Skip to content

Latest commit

 

History

History
88 lines (72 loc) · 2.31 KB

UPGRADE.md

File metadata and controls

88 lines (72 loc) · 2.31 KB
Raw

UPGRADE NOTES

This upgrade sequence has been derived from the Oro(CRM/Commerce). More information can be found at https://oroinc.com/orocrm/doc/current/install-upgrade/upgrade[1] for more details.

Recommended upgrade sequence to Marello 6.0

To retrieve source code of a new version and upgrade your Marello instance, please execute the following steps:

  • Go to the Marello root folder and switch the application to the maintenance mode;
cd /path/to/application
php bin/console lexik:maintenance:lock --env=prod
  • Stop the cron tasks;
crontab -e -uwww-data
  • Comment this line:
*/1 * * * * /usr/bin/php /path/to/application/bin/console --env=prod oro:cron >> /dev/null
  • Stop all running consumers;
  • Create backups of your database and source code;
  • Pull changes from the repository;
git pull
git checkout <VERSION TO UPGRADE>

If you have any customization or third party extensions installed, make sure that:

* your changes to "src/AppKernel.php" file are merged to the new file.
* your changes to "src/" folder are merged and it contains the custom files.
* your changes to "composer.json" file are merged to the new file.
* your changes to configuration files in "config/" folder are merged to the new files.
  • Upgrade composer dependency;
php composer.phar install --prefer-dist --no-dev
  • Remove old caches and assets;
rm -rf var/cache/*
rm -rf public/js/*
rm -rf public/css/*
  • Upgrade platform;
php bin/console oro:platform:update --env=prod --force
  • Remove the caches;
php bin/console cache:clear --env=prod
  • Enable cron;
crontab -e -uwww-data
  • Uncomment this line:
*/1 * * * * /usr/bin/php /path/to/application/bin/console --env=prod oro:cron >> /dev/null
  • Switch your application back to normal mode from the maintenance mode;
php bin/console lexik:maintenance:unlock --env=prod
  • Start the consumers again
php bin/console oro:message-queue:consume --env=prod

Note

If PHP bytecode cache tools (e.g. opcache) are used, PHP-FPM (or Apache web server) should be restarted after the upgrade to flush cached bytecode from the previous installation.