Skip to content

Project lifecycle

1. Bootstrap

codoo init
cd project_name
codoo doctor
codoo core --version 19 --edition community

init creates codoo.json, addons/, config/odoo.conf, and the Docker Compose definition. Odoo source is cached outside the project under ~/.codoo/sources, so multiple projects can reuse it.

2. Prepare a runtime

codoo env use venv
codoo env setup --addons "*" --yes
codoo serve --local
codoo env use docker
codoo env setup --addons "*" --yes
codoo serve --docker

Without --local or --docker, serve uses the runtime saved in codoo.json.

3. Build features

Generate small, reviewable units with the commands in the scaffolding guide. Most generators prompt for missing values and support non-interactive options for automation.

4. Validate and test

codoo lint python --addons "*" --report-dir qa-python
codoo lint xml --addons "*"
codoo lint js --addons "*"
codoo tests up --addons "*"

5. Reproduce dependencies

codoo env lock --addons "*"
codoo env install --addons "*" --frozen

Commit addon requirements.lock.txt files when the team needs deterministic environments.