Extra Addons Repositories

Oduflow supports mounting extra addon repositories (e.g. Odoo Enterprise, third-party themes) into environments. Extra repos are cloned once at the instance level and shared across environments via git worktrees.

Architecture

$ODUFLOW_HOME/
  shared_repos/
    enterprise/          ← bare git clone (shared)
    custom-themes/       ← bare git clone (shared)
  workspaces/
    feature-x/
      repo/              ← main project repo (existing)
      extra/
        enterprise/      ← git worktree (branch 17.0)
        custom-themes/   ← git worktree (branch main)

Setting Up Extra Repos

Clone an extra repository once (it will be available for all environments):

# Via CLI
oduflow call add_extra_repo enterprise https://github.com/odoo/enterprise.git

# Private repos — configure auth first
oduflow call setup_repo_auth https://user:PAT@github.com/odoo/enterprise.git
oduflow call add_extra_repo enterprise https://github.com/odoo/enterprise.git

Using Extra Addons in Environments

When creating an environment, specify which extra repos to mount:

# Mount enterprise addons on branch 17.0
oduflow call create_environment feature-x https://github.com/company/addons.git odoo:17.0 default enterprise 17.0

# Mount multiple extra repos
oduflow call create_environment feature-x https://github.com/company/addons.git odoo:17.0 default "enterprise,custom-themes" 17.0

Oduflow automatically:

  1. Creates a git worktree for each extra repo at the specified branch
  2. Mounts the worktree read-only into the container as /mnt/extra-addons-{name}
  3. Generates a merged odoo.conf with all extra paths added to addons_path

Managing Extra Repos

# List all cloned extra repos with available branches
oduflow call list_extra_repos

# Delete an extra repo (fails if any environment references it)
oduflow call delete_extra_repo enterprise

Extra repos can also be managed from the Web Dashboard under the "Extra Addons" tab.

Updating Extra Repos

Use update_extra_repo to fetch the latest changes from the remote:

oduflow call update_extra_repo enterprise

This runs git fetch --all --prune on the shared bare repository only. It does not affect any running environments.

Why environments are not updated automatically

Each environment gets a detached git worktree pinned to a specific commit at creation time. This is by design:

  • Stability — the environment keeps working with the exact version of extra addons it was deployed with, regardless of upstream changes.
  • Isolation — updating one environment's dependencies cannot break another.
  • Predictability — sync_environment handles only the main project repository; extra addons remain unchanged.

How to update extra addons in an environment

Delete and recreate the environment. The new environment will get a fresh worktree pointing to the latest commit on the specified branch:

oduflow call delete_environment feature-x
oduflow call create_environment feature-x ... "enterprise:17.0"

Tip

Run update_extra_repo before recreating the environment to ensure the bare repo has the latest commits.

results matching ""

    No results matching ""