OCA
/
server-tools
5
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1559 Commits
13 Branches
0 Tags
45 MiB
Tree: 22e81b058e
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '22e81b058e'
${ noResults }
server-tools/module_auto_update/README.rst

77 lines
2.6 KiB
Raw Normal View History

[ADD] module_auto_update: Create module (#882) * [IMP] module_auto_update: Create new module * Add checksum_dir and checksum_installed fields to ir.module.module * Add checksum_dir to compute current checksum of module directory in addons path * Add checksum_installed to store checksum of module directory when module was last installed or upgraded * Use checksumdir Python library to compute module directory sha1 hashes, ignoring pyc and pyo extensions * Extend update_list method to compare modules' checksum_dir and checksum_installed, then change state of modules with differing checksums to 'to upgrade' * Replace Apps/Updates menu item with menu item of same name, which updates apps list and displays tree view of ir.module.module records with state 'to upgrade' * Extend create and write methods to store computed checksum_dir as checksum_installed during module installation and upgrade, and set checksum_installed to False on uninstall * Use context to stop checksum_installed from being updated during upgrade/uninstall cancellation * Add cron job to periodically check for module upgrades by comparing checksums, then perform any available upgrades * Extend upgrade_module method (called by cron and 'Apply Scheduled Upgrades' menu item) to call update_list * Add post_init_hook to store checksum_installed of existing modules * Add test coverage * [FIX] module_auto_update: Fix test broken by changes * Use dummy module to test update_list method instead of module_auto_update
8 years ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
[MIG][module_auto_update] Backport from v10
8 years ago
[ADD] module_auto_update: Create module (#882) * [IMP] module_auto_update: Create new module * Add checksum_dir and checksum_installed fields to ir.module.module * Add checksum_dir to compute current checksum of module directory in addons path * Add checksum_installed to store checksum of module directory when module was last installed or upgraded * Use checksumdir Python library to compute module directory sha1 hashes, ignoring pyc and pyo extensions * Extend update_list method to compare modules' checksum_dir and checksum_installed, then change state of modules with differing checksums to 'to upgrade' * Replace Apps/Updates menu item with menu item of same name, which updates apps list and displays tree view of ir.module.module records with state 'to upgrade' * Extend create and write methods to store computed checksum_dir as checksum_installed during module installation and upgrade, and set checksum_installed to False on uninstall * Use context to stop checksum_installed from being updated during upgrade/uninstall cancellation * Add cron job to periodically check for module upgrades by comparing checksums, then perform any available upgrades * Extend upgrade_module method (called by cron and 'Apply Scheduled Upgrades' menu item) to call update_list * Add post_init_hook to store checksum_installed of existing modules * Add test coverage * [FIX] module_auto_update: Fix test broken by changes * Use dummy module to test update_list method instead of module_auto_update
8 years ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
[MIG][module_auto_update] Backport from v10
8 years ago
[ADD] module_auto_update: Create module (#882) * [IMP] module_auto_update: Create new module * Add checksum_dir and checksum_installed fields to ir.module.module * Add checksum_dir to compute current checksum of module directory in addons path * Add checksum_installed to store checksum of module directory when module was last installed or upgraded * Use checksumdir Python library to compute module directory sha1 hashes, ignoring pyc and pyo extensions * Extend update_list method to compare modules' checksum_dir and checksum_installed, then change state of modules with differing checksums to 'to upgrade' * Replace Apps/Updates menu item with menu item of same name, which updates apps list and displays tree view of ir.module.module records with state 'to upgrade' * Extend create and write methods to store computed checksum_dir as checksum_installed during module installation and upgrade, and set checksum_installed to False on uninstall * Use context to stop checksum_installed from being updated during upgrade/uninstall cancellation * Add cron job to periodically check for module upgrades by comparing checksums, then perform any available upgrades * Extend upgrade_module method (called by cron and 'Apply Scheduled Upgrades' menu item) to call update_list * Add post_init_hook to store checksum_installed of existing modules * Add test coverage * [FIX] module_auto_update: Fix test broken by changes * Use dummy module to test update_list method instead of module_auto_update
8 years ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
  1. .. image:: https://img.shields.io/badge/licence-LGPL--3-blue.svg
  2. :target: http://www.gnu.org/licenses/lgpl-3.0-standalone.html
  3. :alt: License: LGPL-3
  5. ==================
  6. Module Auto Update
  7. ==================
  9. This module will automatically check for and apply module upgrades on a schedule.
  11. Upgrade checking is accomplished by comparing the SHA1 checksums of currently-installed modules to the checksums of corresponding modules in the addons directories.
  13. Installation
  14. ============
  16. Prior to installing this module, you need to:
  18. #. Install checksumdir with `pip install checksumdir`
  19. #. Ensure all installed modules are up-to-date. When installed, this module will assume the versions found in the addons directories are currently installed.
  21. Configuration
  22. =============
  24. The default time for checking and applying upgrades is 3:00 AM (UTC). To change this schedule, modify the "Perform Module Upgrades" scheduled action.
  26. This module will ignore .pyc and .pyo file extensions by default. To modify this, create a module_auto_update.checksum_excluded_extensions system parameter with the desired extensions listed as comma-separated values.
  28. Usage
  29. =====
  31. Modules scheduled for upgrade can be viewed by clicking the "Updates" menu item in the Apps sidebar.
  33. To perform upgrades manually, click the "Apply Scheduled Upgrades" menu item in the Apps sidebar.
  35. .. image:: https://odoo-community.org/website/image/ir.attachment/5784_f2813bd/datas
  36. :alt: Try me on Runbot
  37. :target: https://runbot.odoo-community.org/runbot/149/9.0
  39. Bug Tracker
  40. ===========
  42. Bugs are tracked on `GitHub Issues
  43. <https://github.com/OCA/server-tools/issues>`_. In case of trouble, please
  44. check there if your issue has already been reported. If you spotted it first,
  45. help us smash it by providing detailed and welcomed feedback.
  47. Credits
  48. =======
  50. Images
  51. ------
  53. * Odoo Community Association: `Icon <https://github.com/OCA/maintainer-tools/blob/master/template/module/static/description/icon.svg>`_.
  55. Contributors
  56. ------------
  58. * Brent Hughes <brent.hughes@laslabs.com>
  59. * Juan José Scarafía <jjs@adhoc.com.ar>
  60. * Jairo Llopis <jairo.llopis@tecnativa.com>
  62. Do not contact contributors directly about support or help with technical issues.
  64. Maintainer
  65. ----------
  67. .. image:: https://odoo-community.org/logo.png
  68. :alt: Odoo Community Association
  69. :target: https://odoo-community.org
  71. This module is maintained by the OCA.
  73. OCA, or the Odoo Community Association, is a nonprofit organization whose
  74. mission is to support the collaborative development of Odoo features and
  75. promote its widespread use.
  77. To contribute to this module, please visit https://odoo-community.org.