From d78f807564c39f7cb15f55099c7184d6684adde0 Mon Sep 17 00:00:00 2001 From: Augusto Perez Date: Mon, 4 Sep 2023 13:21:38 +0200 Subject: [PATCH] [ADD] upgrade/on_premise: Add filestore explanation Added a note explaining that the filestores from the upgraded database and the production database have to be merged for on-premise upgrade, on both the testing and the production phases closes odoo/documentation#5727 X-original-commit: 28cacd3b98a540fc716a147c79aa5d557a5a58ae Signed-off-by: Xavier Platteau (xpl) --- content/administration/upgrade/on_premise.rst | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/content/administration/upgrade/on_premise.rst b/content/administration/upgrade/on_premise.rst index d295b7cda..65d1487a2 100644 --- a/content/administration/upgrade/on_premise.rst +++ b/content/administration/upgrade/on_premise.rst @@ -36,6 +36,17 @@ Upgrade request via the Odoo Upgrade Portal - For security reasons, only the person who submitted the upgrade request is able to download it. - Any problem found during testing should be reported via the `helpdesk `_. + - For storage reasons, the copy of your database is submitted without a filestore to the upgrade + server. Therefore, the upgraded database does not contain the production filestore. + - Before restoring the upgraded database, its filestore must be merged with the production + filestore to be able to perform tests in the same conditions as it would be in the new version. + - The upgraded database contains: + + - A `dump.sql` file containing the upgraded database. + - A `filestore` folder containing files that were extracted from in-database records into + attachments (if there are any) and new standard Odoo files from the targeted Odoo version + (like new images, icons, payment provider's logos, etc.). This is the folder that should be + merged with the production filestore in order to get the full upgraded filestore. Upgrade your production database ================================ @@ -44,6 +55,12 @@ Once you have completed the testing successfully, you can proceed to upgrade you production. Download your upgraded database from the link in the email and import it onto your live environment. +.. important:: + - Same as in the test phase, when requesting an upgrade for production purposes, the copy of your + database is submitted without a filestore. + - Therefore, the upgraded database filestore must be merged with the production filestore before + deploying the new version. + Custom modules (if applicable) ==============================