Skip to content

Commit d78f807

Browse files
augustoPerezxpl-odoo
authored andcommitted
[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 #5727 X-original-commit: 28cacd3 Signed-off-by: Xavier Platteau (xpl) <[email protected]>
1 parent 8b7d298 commit d78f807

File tree

1 file changed

+17
-0
lines changed

1 file changed

+17
-0
lines changed

content/administration/upgrade/on_premise.rst

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -36,6 +36,17 @@ Upgrade request via the Odoo Upgrade Portal
3636
- For security reasons, only the person who submitted the upgrade request is able to download it.
3737
- Any problem found during testing should be reported via the `helpdesk
3838
<https://odoo.com/help>`_.
39+
- For storage reasons, the copy of your database is submitted without a filestore to the upgrade
40+
server. Therefore, the upgraded database does not contain the production filestore.
41+
- Before restoring the upgraded database, its filestore must be merged with the production
42+
filestore to be able to perform tests in the same conditions as it would be in the new version.
43+
- The upgraded database contains:
44+
45+
- A `dump.sql` file containing the upgraded database.
46+
- A `filestore` folder containing files that were extracted from in-database records into
47+
attachments (if there are any) and new standard Odoo files from the targeted Odoo version
48+
(like new images, icons, payment provider's logos, etc.). This is the folder that should be
49+
merged with the production filestore in order to get the full upgraded filestore.
3950

4051
Upgrade your production database
4152
================================
@@ -44,6 +55,12 @@ Once you have completed the testing successfully, you can proceed to upgrade you
4455
production. Download your upgraded database from the link in the email and import it onto your live
4556
environment.
4657

58+
.. important::
59+
- Same as in the test phase, when requesting an upgrade for production purposes, the copy of your
60+
database is submitted without a filestore.
61+
- Therefore, the upgraded database filestore must be merged with the production filestore before
62+
deploying the new version.
63+
4764
Custom modules (if applicable)
4865
==============================
4966

0 commit comments

Comments
 (0)