odoo-config
A small CLI that generates an Odoo config file, adapted for the target Odoo
version. Replaces the hand-maintained server.conf template in remoteoi and is
meant to be called as a configuration step by
deploy.py, with per-instance values coming
from deploy.yml.
Local development
Standard template tooling (uv + make):
make install # uv sync + pre-commit install
make check # lock check + pre-commit + ty
make test # pytest
Other tasks: regenerate the CLI reference with
uv run typer odoo_config.main utils docs --name odoo-config --output CLI.md,
and the schema with uv run python scripts/build_schema.py (see Schema below).
Commands
See CLI.md — generated from the code, the source of truth — or
odoo-config <command> --help for every command and flag (including the
--output-format values).
Two behaviours the flag list can't express:
- Ad-hoc overrides: beyond the documented flags, any
--<key>=<value>overrides a single option, e.g.--max-cron-threads=0(dashes → underscores). - Merge precedence, low to high: preset →
--fromfiles → environment →--*overrides.
Schema
The schema is two files, merged at runtime by schema.load_schema():
-
odoo_config/options.toml— the odoo standard: option set, defaults, version availability (min/max_version) and per-version default drift (by_version), mined from Odoo'stools/config.pyacross 13.0–19.0. It is generated (a vendored snapshot, like a lockfile) — do not edit by hand. Regenerate it only when the supported odoo version set changes:uv run python scripts/build_schema.py --odoo /path/to/odoo # or set ODOO_PATH
The odoo root is a parameter, but its layout is fixed: one numeric version directory per version, each holding
odoo/tools/config.py. Limit the set with--versions 17.0,18.0,19.0. -
odoo_config/overlay.toml— the trobz layer: customized defaults, comments, sections (ir.config_parameter,queue_job), presets, and non-core extras (sentry_*, legacy networking, etc.). Edit this freely; changes take effect immediately, no regeneration needed.Dotted keys in presets (e.g.
ir.config_parameteroptions likeribbon.name) must be quoted in TOML so the dot is treated as part of the name, not a sub-table separator:"ribbon.name" = ""— notribbon.name = "".
Overlay values win. A pinned overlay default forces that value on every
version (the mined by_version is dropped); to keep per-version trobz values,
add a [options.<key>.by_version] table in the overlay.
Metadata
Release files for odoo-config 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| odoo_config-0.4.0.tar.gz | 27.8 kB | With provenance | Details for odoo_config-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo_config-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for odoo_config-0.4.0-py3-none-any.whl |
Total release size: 56.6 kB
Release files / odoo_config-0.4.0.tar.gz
| Download URL | odoo_config-0.4.0.tar.gz |
|---|---|
| Size | 27.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1d086b9f83eae42e46d3e32c76ed14d6f10bdfc0c8422d22b01a2a50462cfc6b
|
|
BLAKE2b-256 checksum How to use checksums |
fc56622bea65c62198c69ef99bf74f87303334b815aae3151ecd8c38879c48ae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 30, 2026.
Transparency logRelease files / odoo_config-0.4.0-py3-none-any.whl
| Download URL | odoo_config-0.4.0-py3-none-any.whl |
|---|---|
| Size | 28.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
963b7f4ae6027279335d294d8570b3e3ae911a6f2e85d450b015b42cd30e5c33
|
|
BLAKE2b-256 checksum How to use checksums |
739943bf5470cb11ec43bfbf1e48023f17838b098808b575f626b45909185085
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 30, 2026.
Transparency logSecurity for odoo-config 0.4.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for odoo_config-0.4.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 30, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.