Provides functionalities:

• setup empty new odoo with one bash command odoo init --version 15.0

• setup full fleged odoo server environment containing

  • supports MANIFEST file in odoo root directory to install and uninstall modules
  • postgres with pg_activity, enhanced pgcli
  • fake webmail to receive AND SEND mails
  • logs.io integration to display container output on web browser
  • dividing web, cron, queuejob container per default
  • progress bar on postgres dump/restore

• fzf compatible creation of and AST of your project

• fast restore / create snapshots of complete databases using btrfs, which helps testing things on customer databases

pipx install wodoo

cat << 'EOF' > /etc/sudoers.d/odoo
Cmnd_Alias ODOO_COMMANDS_ODOO = /usr/bin/find *, /var/lib/wodoo_env/bin/odoo *, /usr/bin/btrfs subvolume *, /usr/bin/mkdir *, /usr/bin/mv *, /usr/bin/rsync *, /usr/bin/rm *,  /usr/bin/du *, /usr/local/bin/odoo *, /usr/bin/btrfs subvol show *, /usr/sbin/gosu *
odoo ALL=NOPASSWD:SETENV: ODOO_COMMANDS_ODOO

EOF

odoo init <folder>
cd <folder>
odoo reload
odoo -f db reset
odoo up -d

# now open browser on http://localhost

• make a docker-compose file like ~/.odoo/docker-compose.yml

services:
  odoo3:
    labels:
      compose.merge: base-machine
    environment:
      WHAT YOU WANT
    volumes:
      WHAT YOU WANT

services:
    proxy:
        networks:
            network1:
                ipv4_address: 10.5.0.6
networks:
    network1:
        driver: bridge
        ipam:
            config:
                - subnet: 10.5.0.0/16

services:
    new_machine:
        ...
        labels:
          odoo_framework.apply_env: 0  # do not apply global environment from settings here

• Configure HUB_URL on the pusher side.
• >odoo login
• >odoo build
• >odoo regpush
• All images even base images like redis are pushed; tag name contains SHA name

• Configure REGISTRY=1 in settings and setup HUB_URL
• >odoo login
• >odoo regpull
• All images will be pulled from registry

• nodejs application
• between user browser and odoo
• if odoo is being restarted catches the requests, holds them and releases them to odoo if it is up again
• manages handling of /longpolling path; so if used in custom proxy setups, just refer to that one port here

odoo backup odoo-db <path> (or default name used)
odoo restore odoo-db <path> (or select from list)

odoo pgactivity

Contents will be appended to [options] section of standard odoo configuration.

Configuration may simple look like:

setting1=value1

or like that:

[options]
setting1=value1

[queue_job]
settingqj=valueqj

The [options] is prepended automatically if missed.

To placed in project root.

The used odoo instance must be placed in /odoo.

{
    "server-wide-modules": [
        "web",
        "field_onchange"
    ],
    "version": 17.0,
    "install": [ ...  ],
    "uninstall": [
        "web_tree_many2one_clickable",
        "helpdesk_create_in_new_tab"
    ],
    "devmode_uninstall": [
        "password_security",
    ],
    "tests": [
        "helpdesk_security",
        "visitreports"
    ],
    "addons_paths": [
        "odoo/odoo/addons",
        "odoo/addons",
        "enterprise",
        "addons_tools"
    ]
}

Put #odoo-require: crm,sale_stock in a line in your test

Put #odoo-uninstall: partner_autocomplete in a line in your test

The partner autocomplete nerves for example.

• make files like "Dockerfile.appendix" anywhere in your repo
• to add files, put a directory "Dockerfile.appendix.dir" in the same level; you can access files of it with COPY Dockerfile.appendix.dir/*

If you develop a strange external repository you can define a pre action scripts, that is executed before the reload and you can adapt some things.

Best executed with:

time sudo -E pytest

pipx runpip wodoo install line_profiler
~/.local/pipx/venvs/wodoo/bin/python3 -mkernprof -l -v odoo reload