The project directory layout is identical — backups/, conf/, custom_addons/,
data/, downloads/, odoo/, repositories/, venv/ are all in the same places.
Your existing Odoo installation, databases, and cloned repositories do not need to move.
The only structural change is the project config file:
odoo-helper.conf (Bash variable exports) is replaced by odood.yml (YAML).
Odood can read an existing odoo-helper.conf and generate odood.yml automatically:
# In the root of your existing odoo-helper project
odood discover odoo-helper
# For a system-wide (production) installation managed as root
sudo odood discover odoo-helper --system
This reads odoo-helper.conf, creates odood.yml in the same directory, and sets up the
virtualenv wrapper that Odood needs. Your existing Odoo installation and data are untouched.
When setting up pre-commit on a repository migrated from odoo-helper-scripts, use the
--odoo-helper-compat flag to generate a check-only configuration that matches
odoo-helper’s linting behaviour (no auto-formatting):
Assembly — the recommended way to manage third-party addons on
production servers. Assembly replaces the pattern of cloning multiple repositories
directly on each server.
odood deploy — one-command production deployment with
systemd, nginx, logrotate, fail2ban, and Let’s Encrypt integration.