Smile Upgrade

by
Odoo
v 6.1 v 7.0 v 8.0 v 9.0 v 10.0 v 11.0 v 12.0 Third Party 327
Download for v 6.1
Technical Name smile_upgrade
LicenseSee License tab
Websitehttp://www.smile.fr
Also available in version v 11.0 v 7.0 v 9.0 v 8.0 v 10.0 v 12.0 v 13.0
You bought this module and need support? Click here!

Smile Upgrade

Objectives

  • Allow to upgrade automatically database after code update and server restarting
  • Display a maintenance page instead of home page and kill XML/RPC services during upgrades

Execution

su openerp -c "openerp-server -c rcfile -d db_name --load=web,smile_upgrade"

Configuration

  • Upgrades structure

    <project_directory> `-- upgrades

    |-- 1.1 | |-- __init__.py | |-- __upgrade__.py | |-- *.sql | `-- *.yml # only for post-load |-- 1.2 | |-- __init__.py | |-- __upgrade__.py | `-- *.sql `-- upgrade.conf

  • Upgrades configuration -- upgrade.conf

    [options] version=1.2

  • Upgrade configuration -- __upgrade__.py
    Content: dictonary with the following keys:
    • version
    • databases: let's empty if valid for all databases
    • description
    • modules_to_upgrade: modules list to update or install
    • pre-load: list of .sql files
    • post-load: list with .sql and .yml files
  • OpenERP server configuration -- rcfile=~/.openerp_serverrc

    [options] upgrades_path = <project_directory> stop_after_upgrades = True if you want to stop server after upgrades else False

Additional features

  • In post-load, you can replace filename string by tuple (filename, 'rollback_and_continue' or 'not_rollback_and_continue' or 'raise') -- default value = 'raise'
  • In .yml files, add context['store_in_secure_mode'] = True if you want to compute fields.function (_store_set_values) by catching errors and logging them {record_id: error}

Suggestions & Feedback to: corentin.pouhet-brunerie@smile.fr

Odoo Proprietary License v1.0

This software and associated files (the "Software") may only be used (executed,
modified, executed after modifications) if you have purchased a valid license
from the authors, typically via Odoo Apps, or if you have received a written
agreement from the authors of the Software (see the COPYRIGHT file).

You may develop Odoo modules that use the Software as a library (typically
by depending on it, importing it and using its resources), but without copying
any source code or material from the Software. You may distribute those
modules under the license of your choice, provided that this license is
compatible with the terms of the Odoo Proprietary License (For example:
LGPL, MIT, or proprietary licenses similar to this one).

It is forbidden to publish, distribute, sublicense, or sell copies of the Software
or modified copies of the Software.

The above copyright notice and this permission notice must be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author, please use the developer contact information. They can usually be found in the description.
Please choose a rating from 1 to 5 for this module.