Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Odood Command Reference

odood

Easily manage odoo installations.

Usage:

odood [options] <command>

Options:

FlagDescription
-v, --verboseEnable verbose output
-q, --quietHide unnecessary output
-d, --debugShow additional debug information.
-h, --helpShow this help
--versionShow version

Shortcuts:

NameExpands toDescription
startserver startRun the server in background.
stopserver stopStop the server.
restartserver restartRestart the server.
browseserver browseOpen odoo in browser.
logserver logView server logs.
lsddb listShow databases.
lsaaddons listList addons.
ualaddons update-listUpdate list of addons.
trtranslationsManage translations.

Commands:

  • init — Initialize new odood project.
  • deploy — Deploy production-ready Odoo.
  • server — Server management commands.
  • status — Show the project status.
  • db — Database management commands
  • addons — Manage third-party addons.
  • test — Run tests for modules.
  • repo — Manage git repositories.
  • venv — Manage virtual environment for this project.
  • odoo — Odoo-related utility commands.
  • assembly — Manage assembly of this project
  • script — Run scripts in Odood environment.
  • psql — Run psql for specified database
  • pre-commit — Work with pre-commit dev tool.
  • translations — Manage translations for this project.
  • config — Manage config of the project
  • discover — Discover already installed odoo, and configure Odood to manage it.
  • info — Print info about this Odood project.

odood init

Initialize new odood project.

Usage:

odood init [options]

Options:

FlagDescription
-i, --install-dirDirectory to install odoo to
-v, --odoo-versionVersion of Odoo to install
--install-typeInstallation type. Accept values: git, archive. Default: archive.
--odoo-branchBranch in Odoo repo to install Odoo from.
--odoo-repoInstall Odoo from specific repository.
--pyenvUse python from pyenv to initialize virtualenv for project. Install desired py version if needed
--py-versionInstall specific python version. By default system python used
--node-versionInstall specific node version.
--db-hostDatabase host
--db-portDatabase port
--db-userDatabase user
--db-passwordDatabase password
--create-db-user[sudo] Create database user automatically during installation. Requires sudo.
--http-hostHttp host
--http-portHttp port
--log-to-stderrConfigure project without a log file (logs to stdout/stderr). Recommended for container deployments.
-h, --helpShow this help

odood deploy

Deploy production-ready Odoo.

Usage:

odood deploy [options]

Options:

FlagDescription
-v, --odoo-versionVersion of Odoo to install
--py-versionInstall specific python version.
--node-versionInstall specific node version.
--db-hostDatabase host
--db-portDatabase port
--db-userDatabase user
--db-passwordDatabase password
--local-postgresConfigure local postgresql server (requires PostgreSQL installed)
-w, --workersNumber of workers to apply for this instance. If set to 0, then Odoo will be started in threaded mode. Default: 0
--proxy-modeEnable proxy-mode in odoo config
--local-nginxAutoconfigure local nginx (requires nginx installed)
--local-nginx-server-nameServername for nginx config.
--local-nginx-sslEnable SSL for local nginx
--local-nginx-ssl-certPath to SSL certificate for local nginx.
--local-nginx-ssl-keyPath to SSL key for local nginx.
--tls12-compatAllow TLS 1.2 in addition to TLS 1.3 for backward compatibility with older clients. By default, only TLS 1.3 is enabled.
--letsencryptEnable Let’s Encrypt configuration.
--letsencrypt-emailEmail for Let’s Encrypt account.
--enable-logrotateEnable logrotate for Odoo.
--enable-fail2banEnable fail2ban for Odoo (requires fail2ban installed).
--supervisorWhat supervisor to use for deployment. One of: odood, init-script, systemd. Default: systemd.
--log-to-stderrLog to stderr. Useful when running inside docker.
--use-system-ca-bundleSet REQUESTS_CA_BUNDLE to the system CA certificate store, so Odoo uses system certificates instead of the bundled certifi CA bundle.
--assembly-repoConfigure Odood to use assembly from this repo. Ensure, you have access to specified repo from this machine.
-h, --helpShow this help

odood server

Server management commands.

Usage:

odood server <command>

Options:

FlagDescription
-h, --helpShow this help

Commands:

  • run — Run the server.

  • start — Run the server in background.

  • status — Check if server is running

  • stop — Stop the server

  • restart — Restart the server running in background.

  • browse — Open odoo in browser

  • log — View server logs.

  • healthcheck — Check if the Odoo HTTP server is healthy. Exits 0 if healthy, 1 if not.

  • wait-pg — Wait for PostgreSQL to become available.

odood server run

Run the server.

Usage:

odood server run [options]

Options:

FlagDescription
--ignore-runningIgnore running Odoo instance. (Do not check/create pidfile).
--wait-pgWait for PostgreSQL to be ready before starting the server.
--wait-pg-timeoutMaximum time to wait for PostgreSQL in seconds.
-h, --helpShow this help

odood server start

Run the server in background.

Usage:

odood server start [options]

Options:

FlagDescription
-t, --timeoutTimeout to wait while server starts (in seconds).
-h, --helpShow this help

odood server status

Check if server is running

Usage:

odood server status

Options:

FlagDescription
-h, --helpShow this help

odood server stop

Stop the server

Usage:

odood server stop

Options:

FlagDescription
-h, --helpShow this help

odood server restart

Restart the server running in background.

Usage:

odood server restart [options]

Options:

FlagDescription
-t, --timeoutTimeout to wait while server starts (in seconds).
-h, --helpShow this help

odood server browse

Open odoo in browser

Usage:

odood server browse

Options:

FlagDescription
-h, --helpShow this help

odood server log

View server logs.

Usage:

odood server log

Options:

FlagDescription
-h, --helpShow this help

odood server healthcheck

Check if the Odoo HTTP server is healthy. Exits 0 if healthy, 1 if not.

Usage:

odood server healthcheck [options]

Options:

FlagDescription
-t, --timeoutHTTP request timeout in seconds.
-h, --helpShow this help

odood server wait-pg

Wait for PostgreSQL to become available.

Usage:

odood server wait-pg [options]

Options:

FlagDescription
-t, --timeoutMaximum time to wait in seconds.
--intervalTime between connection attempts in seconds.
-h, --helpShow this help

odood status

Show the project status.

Usage:

odood status

Options:

FlagDescription
-h, --helpShow this help

odood db

Database management commands

Usage:

odood db <command>

Options:

FlagDescription
-h, --helpShow this help

Commands:

  • list — Show the databases available for this odoo instance.
  • create — Create new odoo database.
  • ensure-initialized — Ensure a database exists and is initialized as an Odoo database. Idempotent: safe to use in K8s init containers.
  • drop — Drop the odoo database.
  • exists — Check if database exists.
  • is-initialized — Check if database is initialized as an Odoo database.
  • rename — Rename database.
  • copy — Copy database.
  • backup — Backup database.
  • restore — Restore database.
  • stun — Stun (neutralize) database (disable cron and mail servers).
  • populate — Populate database with test data.

odood db list

Show the databases available for this odoo instance.

Usage:

odood db list

Options:

FlagDescription
-h, --helpShow this help

odood db create

Create new odoo database.

Usage:

odood db create [options] <name>

Options:

FlagDescription
-d, --demoLoad demo data for this db
-r, --recreateRecreate database if it already exists.
--tdbAutomatically generate default name of test database
-l, --langLanguage of database, specified as ISO code of language.
--passwordAdmin password for this database.
--countryCountry for this db.
-i, --installInstall module specified by name.
--install-dirInstall all modules from directory.
--install-fileInstall all modules listed in specified file.
-h, --helpShow this help

Arguments:

NameDescription
nameName of database

odood db ensure-initialized

Ensure a database exists and is initialized as an Odoo database. Idempotent: safe to use in K8s init containers.

Usage:

odood db ensure-initialized [options] <name>

Options:

FlagDescription
--wait-pgWait for PostgreSQL to be ready before proceeding.
--wait-pg-timeoutMaximum time to wait for PostgreSQL in seconds.
-d, --demoLoad demo data (only on first initialization).
-l, --langLanguage code, e.g. en_US (only on first initialization).
-h, --helpShow this help

Arguments:

NameDescription
nameName of database.

odood db drop

Drop the odoo database.

Usage:

odood db drop <name>

Options:

FlagDescription
-h, --helpShow this help

Arguments:

NameDescription
nameName of database(s) to drop.

odood db exists

Check if database exists.

Usage:

odood db exists [options] <name>

Options:

FlagDescription
-q, --quietSuppress output, just return exit code
-h, --helpShow this help

Arguments:

NameDescription
nameName of database

odood db is-initialized

Check if database is initialized as an Odoo database.

Usage:

odood db is-initialized [options] <name>

Options:

FlagDescription
-q, --quietSuppress output, just return exit code.
-h, --helpShow this help

Arguments:

NameDescription
nameName of database.

odood db rename

Rename database.

Usage:

odood db rename <old-name> <new-name>

Options:

FlagDescription
-h, --helpShow this help

Arguments:

NameDescription
old-nameName of original database.
new-nameNew name of database.

odood db copy

Copy database.

Usage:

odood db copy <old-name> <new-name>

Options:

FlagDescription
-h, --helpShow this help

Arguments:

NameDescription
old-nameName of original database.
new-nameNew name of database.

odood db backup

Backup database.

Usage:

odood db backup [options] <name>

Options:

FlagDescription
--zipMake ZIP backup with filestore.
--sqlMake SQL-only backup without filestore
-a, --allBackup all databases
-d, --destDestination path for backup. By default will store at project’s backup directory.
--niceLower the CPU priority of the backup by the given nice increment (1-19, higher = lower priority).
-h, --helpShow this help

Arguments:

NameDescription
nameName of database(s) to backup.

odood db restore

Restore database.

Usage:

odood db restore [options] <name> <backup>

Options:

FlagDescription
--stunStun database (disable cron and mail servers)
--selfishStop the server while database being restored.
-f, --forceEnforce restore, even if backup is not valid.
-r, --recreateRecreate database if it already exists.
-h, --helpShow this help

Arguments:

NameDescription
nameName of database to restore.
backupPath to backup (or name of backup) to restore database from.

odood db stun

Stun (neutralize) database (disable cron and mail servers).

Usage:

odood db stun <name>

Options:

FlagDescription
-h, --helpShow this help

Arguments:

NameDescription
nameName of database to stun.

odood db populate

Populate database with test data.

Usage:

odood db populate [options]

Options:

FlagDescription
-d, --dbnameName of database to populate.
-m, --modelName of model to populate. Could be specified multiple times.
-s, --sizePopulation size
--repeatRepeat population N times.
-h, --helpShow this help

odood addons

Manage third-party addons.

Usage:

odood addons <command>

Options:

FlagDescription
-h, --helpShow this help

Commands:

  • link — Link addons in specified directory.
  • update-list — Update list of addons.
  • list — List addons in specified directory.
  • update — Update specified addons.
  • install — Install specified addons.
  • uninstall — Uninstall specified addons.
  • add — Add addons to the project
  • is-installed — Print list of databases where specified addon is installed.
  • generate-py-requirements — Generate python’s requirements.txt from addon’s manifests. By default, it prints requirements to stdout.
  • find-installed — List addons installed in specified databases

Link addons in specified directory.

Usage:

odood addons link [options] <path>

Options:

FlagDescription
-f, --forceRewrite already linked/existing addon.
-r, --recursiveSearch for addons in this directory recursively.
--manifest-requirementsInstall python dependencies from manifest’s external dependencies
--individual-requirementsInstall Python requirements per-addon instead of batched
--with-odoo-requirementsInclude Odoo’s requirements.txt in the batch install
--ualUpdate addons list for all databases
-h, --helpShow this help

Arguments:

NameDescription
pathPath to search for addons in.

odood addons update-list

Update list of addons.

Usage:

odood addons update-list [options] <database>

Options:

FlagDescription
-a, --allUpdate all databases.
-h, --helpShow this help

Arguments:

NameDescription
databaseDatabase(s) to update addons list for.

odood addons list

List addons in specified directory.

Usage:

odood addons list [options] <path>

Options:

FlagDescription
--by-pathDisplay addons by paths.
--by-nameDisplay addons by name (default).
--by-name-versionDisplay addon name with addon version
-s, --systemSearch for all addons available for Odoo.
-r, --recursiveSearch for addons recursively.
--installableFilter only installable addons.
--not-installableFilter only not-installable addons.
--linkedFilter only linked addons.
--not-linkedFilter only addons that are not linked.
--with-priceFilter only addons that has price defined.
--without-priceFilter only addons that does not have price defined.
--assemblyShow addons available in assembly
-t, --tableDisplay list of addons as table
-f, --fieldDisplay provided field in table. This have to be valid field from manifest.
-c, --colorColor output by selected scheme: link - color addons by link status, installable - color addons by installable state.
-h, --helpShow this help

Arguments:

NameDescription
pathPath to search for addons in.

odood addons update

Update specified addons.

Usage:

odood addons update [options] <addon>

Options:

FlagDescription
-d, --dbDatabase(s) to apply operation to.
--dirDirectory to search for addons
--dir-rDirectory to recursively search for addons
-f, --fileRead addons names from file (addon names must be separated by new lines)
--assemblySearch for addons available in assembly
--skipSkip addon specified by name.
--skip-reSkip addon specified by regex.
--skip-fileSkip addons listed in specified file (addon names must be separated by new lines)
--skip-errorsDo not fail on errors during installation.
--ignore-unfinished-updatesDo not fail if there are unfinished addon install/update/uninstall operations.
--startStart server after update (if everything is ok)
--ualUpdate addons list before update.
-a, --allUpdate all modules
--installed-onlySkip addons that are not installed in the database.
-h, --helpShow this help

Arguments:

NameDescription
addonNames of addons to operate on.

odood addons install

Install specified addons.

Usage:

odood addons install [options] <addon>

Options:

FlagDescription
-d, --dbDatabase(s) to apply operation to.
--dirDirectory to search for addons
--dir-rDirectory to recursively search for addons
-f, --fileRead addons names from file (addon names must be separated by new lines)
--assemblySearch for addons available in assembly
--skipSkip addon specified by name.
--skip-reSkip addon specified by regex.
--skip-fileSkip addons listed in specified file (addon names must be separated by new lines)
--skip-errorsDo not fail on errors during installation.
--ignore-unfinished-updatesDo not fail if there are unfinished addon install/update/uninstall operations.
--startStart server after update (if everything is ok)
--ualUpdate addons list before install.
--missing-onlySkip addons that are already installed in the database.
-h, --helpShow this help

Arguments:

NameDescription
addonNames of addons to operate on.

odood addons uninstall

Uninstall specified addons.

Usage:

odood addons uninstall [options] <addon>

Options:

FlagDescription
-d, --dbDatabase(s) to apply operation to.
--dirDirectory to search for addons
--dir-rDirectory to recursively search for addons
-f, --fileRead addons names from file (addon names must be separated by new lines)
--assemblySearch for addons available in assembly
--skipSkip addon specified by name.
--skip-reSkip addon specified by regex.
--skip-fileSkip addons listed in specified file (addon names must be separated by new lines)
--skip-errorsDo not fail on errors during installation.
--ignore-unfinished-updatesDo not fail if there are unfinished addon install/update/uninstall operations.
--startStart server after update (if everything is ok)
-h, --helpShow this help

Arguments:

NameDescription
addonNames of addons to operate on.

odood addons add

Add addons to the project

Usage:

odood addons add [options]

Options:

FlagDescription
--single-branchClone repository with –single-branch options. This could significantly reduce size of data to be downloaded and increase performance.
-r, --recursiveRecursively process odoo_requirements.txt. If set, then Odood will automatically process odoo_requirements.txt file inside repositories mentioned in provided odoo_requirements.txt
--manifest-requirementsInstall python dependencies from manifest’s external dependencies
--odoo-appsAdd addon from odoo apps.
--odoo-requirementsAdd modules (repos) from odoo_requirements.txt file (or directory containing odoo_requirements.txt), that is used by odoo-helper-scripts.
-h, --helpShow this help

odood addons is-installed

Print list of databases where specified addon is installed.

Usage:

odood addons is-installed <addon>

Options:

FlagDescription
-h, --helpShow this help

Arguments:

NameDescription
addonName of addon or path to addon to check.

odood addons generate-py-requirements

Generate python’s requirements.txt from addon’s manifests. By default, it prints requirements to stdout.

Usage:

odood addons generate-py-requirements [options] <addon>

Options:

FlagDescription
-o, --out-filePath to file where to store generated requirements
--dirDirectory to search for addons to generate requirements.txt for.
--dir-rDirectory to recursively search for addons to generate requirements.txt for.
-h, --helpShow this help

Arguments:

NameDescription
addonName of addon to generate requirements for.

odood addons find-installed

List addons installed in specified databases

Usage:

odood addons find-installed [options]

Options:

FlagDescription
-d, --dbName of database to check for addons.
-o, --out-filePath to file where to store result
-f, --formatOutput format. One of: list, assembly-spec. Default: list.
-a, --allCheck all databases
--non-systemList only custom addons, that are not default Odoo addons.
-h, --helpShow this help

odood test

Run tests for modules.

Usage:

odood test [options] <addon>

Options:

FlagDescription
-t, --temp-dbCreate temporary database for tests.
--no-drop-dbDo not drop temporary database after test completed.
--iswIgnore warnings that are considered safe.
--simplified-logDisplay simplified log messages.
--migrationRun migration against stable branch.
--coverageCalculate code coverage.
--coverage-reportPrint coverage report.
--coverage-htmlPrepare HTML report for coverage.
--coverage-skip-coveredSkip covered files in coverage report.
--coverage-ignore-errorsIgnore coverage errors.
--coverage-fail-underFail if coverage is less than specified value.
--no-error-reportDo not print error report in the end of the test.
--error-reportPrint error report in the end of the test.
--warning-reportPrint warning report in the end of the test.
-d, --dbDatabase to run tests for.
--additional-addonSpecify additional addon to install before test.
--no-install-addonsDo not install addons before test. Could be useful to speed up local tests.
--dirDirectory to search for addons to test
--dir-rDirectory to recursively search for addons to test
-f, --fileRead addons names from file (addon names must be separated by new lines)
--skipSkip (do not run tests) addon specified by name.
--skip-reSkip (do not run tests) addon specified by regex.
--skip-fileSkip addons listed in specified file (addon names must be separated by new lines)
--migration-start-refgit reference (branch/commit/tag) to start migration from
--migration-reporun migration tests for repo specified by path
--migration-last-releaseStart migration test from the latest release tag. Fails if no release tags exist for the current Odoo serie.
--populate-modelName of model to populate. Could be specified multiple times.
--populate-sizePopulation size.
--test-tagFilter tests by tag (Odoo 12.0+). Repeatable. Supports Odoo tag syntax: plain tags, /module, /module:Class.method, -tag to exclude.
-h, --helpShow this help

Arguments:

NameDescription
addonNames of addons to run tests for.

odood repo

Manage git repositories.

Usage:

odood repo <command>

Options:

FlagDescription
-h, --helpShow this help

Commands:

  • add — Add git repository to Odood project.
  • pull-all — [Experimental] Pull changes from all repos and relink addons.
  • fix-version-conflict — Fix version conflicts in manifests of addons in this repo.
  • fix-series — Fix series in manifests of addons in this repo. Set series to project’s serie
  • bump-versions — Bump versions for modules that have changes (comparably to stable branch).
  • check-versions — Check changed addons has updated versions.
  • migrate-addons — Migrate code of addons that has older odoo serie to serie of this project.
  • do-forward-port — [Experimental] Do forwardport changes from older branch.
  • release — Release addon repository: auto-version, tag, and optionally push.
  • hotfix — Manage hotfix (patch) releases on dedicated hotfix branches.

odood repo add

Add git repository to Odood project.

Usage:

odood repo add [options] <repo>

Options:

FlagDescription
--ocaAdd Odoo Community Association (OCA) repository. If set, then ‘repo’ argument could be specified as name of repo under ‘https://github.com/OCA’ organization.
--githubAdd github repository. If set, then ‘repo’ argument could be specified as ‘owner/name’ that will be converted to ‘https://github.com/owner/name’.
--single-branchClone repository with –single-branch options. This could significantly reduce size of data to be downloaded and increase performance.
-r, --recursiveIf set, then system will automatically fetch recursively dependencies of this repository, specified in odoo_requirements.txt file inside cloned repo.
-b, --branchBranch to clone
--ualUpdate addons list.
-h, --helpShow this help

Arguments:

NameDescription
repoRepository URL to clone from.

odood repo pull-all

[Experimental] Pull changes from all repos and relink addons.

Usage:

odood repo pull-all

Options:

FlagDescription
-h, --helpShow this help

odood repo fix-version-conflict

Fix version conflicts in manifests of addons in this repo.

Usage:

odood repo fix-version-conflict <path>

Options:

FlagDescription
-h, --helpShow this help

Arguments:

NameDescription
pathPath to repository to fix conflicts in.

odood repo fix-series

Fix series in manifests of addons in this repo. Set series to project’s serie

Usage:

odood repo fix-series <path>

Options:

FlagDescription
-h, --helpShow this help

Arguments:

NameDescription
pathPath to repository to fix conflicts in.

odood repo bump-versions

Bump versions for modules that have changes (comparably to stable branch).

Usage:

odood repo bump-versions [options] <path>

Options:

FlagDescription
--majorIncrease major version for addons.
--minorIncrease minor version for addons.
--patchIncrease patch version for addons.
--ignore-translationsIgnore translations.
-h, --helpShow this help

Arguments:

NameDescription
pathPath to repository to search for addons to bump versions.

odood repo check-versions

Check changed addons has updated versions.

Usage:

odood repo check-versions [options] <path>

Options:

FlagDescription
--ignore-translationsIgnore translations.
--since-last-releaseCompare against the latest release tag instead of the stable branch tip. Shows exactly what ‘odood repo release’ will verify.
-h, --helpShow this help

Arguments:

NameDescription
pathPath to repository to search for addons to bump versions.

odood repo migrate-addons

Migrate code of addons that has older odoo serie to serie of this project.

Usage:

odood repo migrate-addons [options] <path>

Options:

FlagDescription
-m, --moduleName of module to migrate
--commitCommit changes.
-h, --helpShow this help

Arguments:

NameDescription
pathPath to repository to migrate addons in.

odood repo do-forward-port

[Experimental] Do forwardport changes from older branch.

Usage:

odood repo do-forward-port [options] <path>

Options:

FlagDescription
-s, --sourceSource branch to forwardport changes from
-h, --helpShow this help

Arguments:

NameDescription
pathPath to repository to migrate addons in.

odood repo release

Release addon repository: auto-version, tag, and optionally push.

Usage:

odood repo release [options] <path>

Options:

FlagDescription
--initialCreate the first release for a repository with no prior tags at version .1.0.0. Skips change detection and version checking.
--majorForce a major version bump.
--minorForce a minor version bump.
--patchForce a patch version bump.
--ignore-translationsIgnore translation files (.po/.pot) when detecting changes.
--fail-nothing-to-releaseExit with code 1 when no changed addons are detected.
--pushPush the release tag (and branch) to origin.
--changelogGenerate CHANGELOG.md and CHANGELOG.latest.md and commit them before tagging.
--commit-messageCommit message for the changelog commit (default: ‘Release ’).
--commit-userGit author name for the changelog commit.
--commit-emailGit author email for the changelog commit.
-h, --helpShow this help

Arguments:

NameDescription
pathPath to repository to release (default: current directory).

odood repo hotfix

Manage hotfix (patch) releases on dedicated hotfix branches.

Usage:

odood repo hotfix <command>

Options:

FlagDescription
-h, --helpShow this help

Commands:

  • start — Set up a hotfix branch from a primary release tag. Run this before ‘odood repo hotfix release’.
  • check — Check addon versions on the current hotfix branch against the latest tag in its patch chain. Previews what ‘odood repo hotfix release’ will verify.
  • release — Release a hotfix (patch) on the current hotfix branch: bump Z on top of the chain’s latest tag, tag, and optionally push.
odood repo hotfix start

Set up a hotfix branch from a primary release tag. Run this before ‘odood repo hotfix release’.

Usage:

odood repo hotfix start [options] <path>

Options:

FlagDescription
--fromPrimary release tag to patch (e.g. 18.0.2.1.0). Must have Z == 0.
-h, --helpShow this help

Arguments:

NameDescription
pathPath to repository (default: current directory).
odood repo hotfix check

Check addon versions on the current hotfix branch against the latest tag in its patch chain. Previews what ‘odood repo hotfix release’ will verify.

Usage:

odood repo hotfix check [options] <path>

Options:

FlagDescription
--ignore-translationsIgnore translation files (.po/.pot) when detecting changes.
-h, --helpShow this help

Arguments:

NameDescription
pathPath to repository (default: current directory).
odood repo hotfix release

Release a hotfix (patch) on the current hotfix branch: bump Z on top of the chain’s latest tag, tag, and optionally push.

Usage:

odood repo hotfix release [options] <path>

Options:

FlagDescription
--ignore-translationsIgnore translation files (.po/.pot) when detecting changes.
--fail-nothing-to-releaseExit with code 1 when no changed addons are detected.
--pushPush the release tag (and branch) to origin.
--changelogGenerate CHANGELOG.md and CHANGELOG.latest.md and commit them before tagging.
--commit-messageCommit message for the changelog commit (default: ‘Release ’).
--commit-userGit author name for the changelog commit.
--commit-emailGit author email for the changelog commit.
-h, --helpShow this help

Arguments:

NameDescription
pathPath to repository (default: current directory).

odood venv

Manage virtual environment for this project.

Usage:

odood venv <command>

Options:

FlagDescription
-h, --helpShow this help

Commands:

  • install-dev-tools — Install Dev Tools
  • install-py-packages — Install Python packages
  • reinstall — Reinstall virtualenv.
  • update-odoo — Update Odoo itself.
  • reinstall-odoo — Reinstall Odoo to different Odoo version.
  • pip — Run pip for this environment. All arguments after ‘–’ will be forwarded directly to pip.
  • npm — Run npm for this environment. All arguments after ‘–’ will be forwarded directly to npm.
  • ipython — Run ipython in this environment. All arguments after ‘–’ will be forwarded directly to IPython.
  • python — Run python for this environment. All arguments after ‘–’ will be forwarded directly to python.
  • lodoo — Run lodoo in this environment. All arguments after ‘–’ will be forwarded directly to lodoo.
  • run — Run command in this virtual environment. The command and all arguments must be specified after ‘–’. For example: ‘odood venv run – ipython’

odood venv install-dev-tools

Install Dev Tools

Usage:

odood venv install-dev-tools

Options:

FlagDescription
-h, --helpShow this help

odood venv install-py-packages

Install Python packages

Usage:

odood venv install-py-packages [options] <package>

Options:

FlagDescription
-r, --requirementsPath to requirements.txt to install python packages from
-h, --helpShow this help

Arguments:

NameDescription
packagePython package specification to install.

odood venv reinstall

Reinstall virtualenv.

Usage:

odood venv reinstall [options]

Options:

FlagDescription
--py-versionInstall specific python version.
--node-versionInstall specific node version.
-h, --helpShow this help

odood venv update-odoo

Update Odoo itself.

Usage:

odood venv update-odoo [options]

Options:

FlagDescription
-b, --backupBackup Odoo before update.
-h, --helpShow this help

odood venv reinstall-odoo

Reinstall Odoo to different Odoo version.

Usage:

odood venv reinstall-odoo [options]

Options:

FlagDescription
-b, --backupBackup Odoo before update.
--no-backupDo not take backup of Odoo and venv.
--venv-py-versionInstall specific python version.
--venv-node-versionInstall specific node version.
--install-typeInstallation type. Accept values: git, archive. Default: archive.
-v, --versionOdoo version to install.
-h, --helpShow this help

odood venv pip

Run pip for this environment. All arguments after ‘–’ will be forwarded directly to pip.

Usage:

odood venv pip

Options:

FlagDescription
-h, --helpShow this help

odood venv npm

Run npm for this environment. All arguments after ‘–’ will be forwarded directly to npm.

Usage:

odood venv npm

Options:

FlagDescription
-h, --helpShow this help

odood venv ipython

Run ipython in this environment. All arguments after ‘–’ will be forwarded directly to IPython.

Usage:

odood venv ipython

Options:

FlagDescription
-h, --helpShow this help

odood venv python

Run python for this environment. All arguments after ‘–’ will be forwarded directly to python.

Usage:

odood venv python

Options:

FlagDescription
-h, --helpShow this help

odood venv lodoo

Run lodoo in this environment. All arguments after ‘–’ will be forwarded directly to lodoo.

Usage:

odood venv lodoo

Options:

FlagDescription
-h, --helpShow this help

odood venv run

Run command in this virtual environment. The command and all arguments must be specified after ‘–’. For example: ‘odood venv run – ipython’

Usage:

odood venv run

Options:

FlagDescription
-h, --helpShow this help

odood odoo

Odoo-related utility commands.

Usage:

odood odoo <command>

Options:

FlagDescription
-h, --helpShow this help

Commands:

  • shell — Run an interactive Odoo shell.
  • recompute — Recompute stored fields for a model.

odood odoo shell

Run an interactive Odoo shell.

Usage:

odood odoo shell [options]

Options:

FlagDescription
-d, --dbDatabase to run shell for.
-h, --helpShow this help

odood odoo recompute

Recompute stored fields for a model.

Usage:

odood odoo recompute [options]

Options:

FlagDescription
-f, --fieldName of field to recompute.
-d, --dbName of database to recompute fields for.
--all-dbRecompute for all databases.
-m, --modelName of model to recompute fields for
-h, --helpShow this help

odood assembly

Manage assembly of this project

Usage:

odood assembly [options] <command>

Options:

FlagDescription
-p, --assembly-pathPath to assembly directory.
-h, --helpShow this help

Commands:

  • init — Initialize assembly for this project
  • use — Use (attach) assembly located at specified path. Mostly useful in CI flows.
  • status — Project assembly status
  • sync — Synchronize assembly with updates from sources.
  • link — Link addons from this assembly to custom addons
  • pull — Pull updates for this assembly.
  • upgrade — Upgrade assembly (optionally do backup, pull changes, update addons).
  • upgrade-sources — Upgrade assembly source refs to the latest version tags on their remotes.

odood assembly init

Initialize assembly for this project

Usage:

odood assembly init [options]

Options:

FlagDescription
--repoUrl to git repo with assembly to use for this project.
-h, --helpShow this help

odood assembly use

Use (attach) assembly located at specified path. Mostly useful in CI flows.

Usage:

odood assembly use <path>

Options:

FlagDescription
-h, --helpShow this help

Arguments:

NameDescription
pathPath to already existing assembly.

odood assembly status

Project assembly status

Usage:

odood assembly status

Options:

FlagDescription
-h, --helpShow this help

odood assembly sync

Synchronize assembly with updates from sources.

Usage:

odood assembly sync [options]

Options:

FlagDescription
--commitCommit changes.
--commit-messageCommit message
--commit-userName of user to use for commit
--commit-emailEmail of user to use for commit
--fail-nothing-to-commitFail (set exit code = 1) if there is nothing to commit
--pushAutomatically push changes if needed.
--push-toName of branch to push changes to.
--changelogGenerate changelog for assembly.
--dockerfileGenerate Dockerfile for assembly.
--generate-lockGenerate requirements.lock.txt after syncing
--with-odoo-requirementsInclude Odoo’s requirements.txt when generating lock file
-h, --helpShow this help

Link addons from this assembly to custom addons

Usage:

odood assembly link [options]

Options:

FlagDescription
--manifest-requirementsInstall python dependencies from manifest’s external dependencies
--individual-requirementsInstall Python requirements per-addon instead of batched
--with-odoo-requirementsInclude Odoo’s requirements.txt in the batch install
--ualUpdate addons list for all databases
-h, --helpShow this help

odood assembly pull

Pull updates for this assembly.

Usage:

odood assembly pull [options]

Options:

FlagDescription
--linkRelink addons in this assembly after pull
-h, --helpShow this help

odood assembly upgrade

Upgrade assembly (optionally do backup, pull changes, update addons).

Usage:

odood assembly upgrade [options]

Options:

FlagDescription
--backupDo backup of all databases
--skip-errorsContinue upgrade next databases if upgrade of db had error.
--startStart the server if upgrade completed successfully and server was not running before upgrade.
-h, --helpShow this help

odood assembly upgrade-sources

Upgrade assembly source refs to the latest version tags on their remotes.

Usage:

odood assembly upgrade-sources [options]

Options:

FlagDescription
--commitCommit the updated spec.
--commit-messageCommit message.
--commit-userName of user to use for commit.
--commit-emailEmail of user to use for commit.
--pushPush changes after committing.
--push-toName of branch to push changes to.
-h, --helpShow this help

odood script

Run scripts in Odood environment.

Usage:

odood script <command>

Options:

FlagDescription
-h, --helpShow this help

Commands:

  • py — Run Python script in this environment.
  • sql — Run SQL script in this environment.

odood script py

Run Python script in this environment.

Usage:

odood script py [options] <script>

Options:

FlagDescription
-d, --dbDatabase to run script for
-h, --helpShow this help

Arguments:

NameDescription
scriptPath to script to run

odood script sql

Run SQL script in this environment.

Usage:

odood script sql [options] <script>

Options:

FlagDescription
-d, --dbDatabase to run script for
-n, --no-commitDo not commit changes.
-h, --helpShow this help

Arguments:

NameDescription
scriptPath to script to run

odood psql

Run psql for specified database

Usage:

odood psql [options]

Options:

FlagDescription
-d, --dbName of database to connect to.
-h, --helpShow this help

odood pre-commit

Work with pre-commit dev tool.

Usage:

odood pre-commit <command>

Options:

FlagDescription
-h, --helpShow this help

Commands:

  • init — Initialize pre-commit for this repo.
  • set-up — Set up pre-commit for specified repo.
  • update — Update pre-commit for specified repo.
  • run — Run pre-commit for specified repo.

odood pre-commit init

Initialize pre-commit for this repo.

Usage:

odood pre-commit init [options] <path>

Options:

FlagDescription
-f, --forceEnforce initialization. This will rewrite pre-commit configurations.
--no-setupDo not set up pre-commit. Could be used if pre-commit already set up.
--odoo-helper-compatGenerate pre-commit config compatible with odoo-helper linting style (check-only, no auto-formatting).
-h, --helpShow this help

Arguments:

NameDescription
pathPath to repository to initialize pre-commit.

odood pre-commit set-up

Set up pre-commit for specified repo.

Usage:

odood pre-commit set-up <path>

Options:

FlagDescription
-h, --helpShow this help

Arguments:

NameDescription
pathPath to repository to configure.

odood pre-commit update

Update pre-commit for specified repo.

Usage:

odood pre-commit update <path>

Options:

FlagDescription
-h, --helpShow this help

Arguments:

NameDescription
pathPath to repository to configure.

odood pre-commit run

Run pre-commit for specified repo.

Usage:

odood pre-commit run <path>

Options:

FlagDescription
-h, --helpShow this help

Arguments:

NameDescription
pathPath to repository to run pre-commit for.

odood translations

Manage translations for this project.

Usage:

odood translations <command>

Options:

FlagDescription
-h, --helpShow this help

Commands:

  • regenerate — Regenerate translations for specified addons.

odood translations regenerate

Regenerate translations for specified addons.

Usage:

odood translations regenerate [options] <addon>

Options:

FlagDescription
--pot-remove-datesRemove dates from generated .pot file.
--potGenerate .pot file for translations.
--pot-updateUpdate translations based on regenerated .pot file.
--missing-onlyGenerate only missing translations.
--no-drop-dbDo not drop database after regeneration of translations
--addon-dirDirectory to search for addons
--addon-dir-rDirectory to recursively search for addons
--lang-fileCombination of lang and file (separated by ‘:’) to generate translations for. For example: uk_UA:uk.
-l, --langLanguage to generate translations for. For example: uk_UA.
-h, --helpShow this help

Arguments:

NameDescription
addonNames of addons to regenerate translations for.

odood config

Manage config of the project

Usage:

odood config <command>

Options:

FlagDescription
-h, --helpShow this help

Commands:

  • update — Update the config.

odood config update

Update the config.

Usage:

odood config update

Options:

FlagDescription
-h, --helpShow this help

odood discover

Discover already installed odoo, and configure Odood to manage it.

Usage:

odood discover <command>

Options:

FlagDescription
-h, --helpShow this help

Commands:

  • odoo-helper — Discover odoo-helper-scripts project.

odood discover odoo-helper

Discover odoo-helper-scripts project.

Usage:

odood discover odoo-helper [options] <path>

Options:

FlagDescription
-s, --systemDiscover system (server-wide) odoo-helper project installation.
-h, --helpShow this help

Arguments:

NameDescription
pathTry to discover odoo-helper project in specified path.

odood info

Print info about this Odood project.

Usage:

odood info [options]

Options:

FlagDescription
--jsonPrint output in json format
-h, --helpShow this help