Dockerized Odoo
This is a flexible and streamlined version of most dockerized Odoo projects that you'll find. And one that allows you to deploy with two different methods using the same Dockerfile:
- Standalone: As most people use their implementation. With Odoo's source code inside the container. This is the default
- Hosted: A more practical deployment for development, as the HOST (where docker is installed) has the source code, and each container uses this single source.
Dockerdoo is integrated with VSCode for fast development and debugging, just install the Remote Containers extension.
By default this approach does not use the modules availables at the
./custom
directory, as this uses Docker's hosted volumes approach which is considerably slow on Mac and PC. If you'd like to use it this way, just uncomment./custom:${ODOO_EXTRA_ADDONS}:delegated
from thedev-vscode.yml
Quick usage
To use the hosted approach, the Odoo code must be in the ./src
directory, if you also use Enterprise you can add it to the custom
directory, which is automagically added to your addons_path.
Project Structure
your-project/
├── resources/ # Scripts for service automation
├── src/
│ └── odoo/ # Just required if using hosted source code
│
├── config/
│ └── odoo.conf # Hosted configuration file for hosted environment
├── custom/ # Custom modules goes here, same level hierarchy **REQUIRED**
│ ├── custom/
│ ├── OCA/
│ ├── enterprise/
│ └── /
├── ... # Common files (.gitignore, etc.)
├── .env # Single source of environment definition
├── Dockerfile # Single source of image definition
├── docker-compose.yml # The opionated version
└── docker-compose.override.yml # Your custom version
Extra addons
You can put all your custom addons in the folder ./custom/
, those will be automatically added to your addons_path
thanks to the script in ./resources/getaddons.py
Credits
Mainly based on dockery-odoo work by:
Bunch of ideas taken from:
WIP
- Swarm / Kubernetes considerations (secrets, etc.)