From 165f3a5494564d370c8ad7ce44676bfaf5679c9b Mon Sep 17 00:00:00 2001 From: Luc PIERSON Date: Tue, 29 Jul 2025 09:53:39 +0200 Subject: [PATCH] Update 4 README.md --- README.md | 44 ++++++++++++++++++++++---------------------- 1 file changed, 22 insertions(+), 22 deletions(-) diff --git a/README.md b/README.md index a86eb66..4d5eb5b 100644 --- a/README.md +++ b/README.md @@ -7,56 +7,56 @@ This is a description of the actions I did to upgrade a odoo community v17 to v1 0) to avoid any module problem, remove the custom V17 installations: - in the odoo env, go to apps, look for all modules installed and remove the custom ones. You may find the list in your ./custom (the folder which links to /mnt/extra-addons in your docker-compose) -1) upgrade your current env to last V17 version (see in V187 folder): - - a) with provided latest V18 Dokerfile, entrypoint.sh and wait-for-psql.py, create new image, run existing V17 on a docker from that new image - - see in V17 folder the build command and docker-compose.yml odoo.conf related - - remember on which docker runs your pstgres (in my case postgres-20250725-mylucdatabase) +2) upgrade your current env to last V17 version (see in V17 folder): + - with provided latest V17 Dokerfile, entrypoint.sh and wait-for-psql.py, create new image, run existing V17 on a docker from that new image + * see in V17 folder the build command and docker-compose.yml odoo.conf related + * remember on which docker runs your pstgres (in my case postgres-20250725-mylucdatabase) -3) Create a Migration env based on V18 (see in V18-MIG folder): - - you need a dedicated Dockerfile based on latest provided odoo V18 (in my case 20250725) - - a) update your V18 Dockerfile +4) Create a Migration env based on V18 called V18-MIG (with provided latest V18 Dokerfile): + + a) update your V18-MIG Dockerfile - add vim, curl, git, unzip in the early installation - create a directory for OpenUpgrade scripts (line 95) - add the install of openupgradelib (line 96) - add the reference to directory /var/lib/odoo/OpenUpgrade (line 98) - b) update your v18 entrypoint.sh + b) update your V18-MIG entrypoint.sh - you need to add the migration instruction (see at the end) - c) update you docker-compose.yml + c) created or update you V18-MIG docker-compose.yml - - you need to run once only (no restart) - - you need to add reference to the local unzipped folder V18 OpenUpgrade + - you need to run once only (==> no restart) + - you need to add reference to the local ./OpenUpgrade - d) update your odoo.conf with references to the running postgresql + d) update your V18-MIG odoo.conf with references to the running postgresql - you need to reference your V17 postgresql running docker and the db_name to migrate - you need to add variables - e) download the OCA OpenUpgrade Scripts + e) download the OCA OpenUpgrade Scripts in your V18-MIG folder - download and unzip or git clone the OpenUpgrade V18 env to the local folder (in my case ./OpenUpgrade/ ) e) run the migration: + - Build your image for migration (see command in build.odoo.image.txt) - launch the docker (docker-compose up -d) - monitor the logs (tail -f ./logs/odoo.log) -5) Create a V18 env based on V18 (see in V18 folder): +6) Create a V18 env based on V18 (see in V18 folder): - - Based on latest Dokerfile, entrypoint.sh and wait-for-psql.py - - copy the filestore content to the new V18 env - - Create your docker image - - run the new v18 docker and monitor the logs (tail -f ./logs/odoo.log) + - Get the latest V18 Dokerfile, entrypoint.sh and wait-for-psql.py + - copy the odoo-filestore content to the new V18 folder + - Build your docker image + - Create your docker-compose.yml with only the odoo service (postgres already running) + - run the new V18 docker (docker-compose up -d) + - monitor the logs (tail -f ./logs/odoo.log) links : - docker images : https://hub.docker.com/_/odoo + odoo Docker images : https://hub.docker.com/_/odoo OCA Openupgrade : https://github.com/OCA/OpenUpgrade/tree/18.0 This is provided as indication only, HTH, best, Luc