Skip to content

Latest commit

 

History

History
24 lines (14 loc) · 950 Bytes

UPGRADE.md

File metadata and controls

24 lines (14 loc) · 950 Bytes
Raw

Upgrading

Based on the original Wiki content at http://code.google.com/p/openclerk/wiki/Upgrading. Also see the pending issue for developing an upgrade script: #115

Upgrading an Openclerk instance is currently a manual process but fairly straightforward once you have done it a couple of times. The basic format is:

  1. Update config.php and set jobs_enabled to false

  2. Execute git pull to update to the latest version

  3. Run composer update to update any composer dependencies

  4. Run npm update to update any NPM dependencies

  5. Execute grunt deploy to rebuild static assets

  6. Execute php -f core/install.php, or visit the Admin page Install latest migrations, to upgrade the database

  7. Re-enable jobs_enabled to true

  8. Check the admin status page to make sure that no jobs are failing with errors, fix configuration as necessary