I am deploying Odoo 15 with Docker, and I am using the docker-compose.yml
recommended in https://hub.docker.com/_/odoo. As you can see, the following volumes are created for the web service:
volumes:
- odoo-web-data:/var/lib/odoo
- ./config:/etc/odoo
- ./addons:/mnt/extra-addons
The conclusion here is that there is a volume named odoo-web-data
for the Odoo core, and two binds, which I guess they are in order to modify easily the configuration file and the extra addons.
If I expect to add a lot of modules in the local directory addons
, in order to add those modules to the container directory extra-addons
, and therefore adding them to the Odoo running in the container, does it make sense to add them this way?
For example, I am going to add the whole Odoo Community Association l10n-spain
repository from GitHub (with all their addons), among others. Obviously I will do git pull
every now and again to update the repository.
As I am not an expert on Docker, do you think this structure is the best? What if I need to update the Odoo core in the named volume?