End-to-end on the live onebspace deployment: container now listens on 0.0.0.0:8069, preview domain returns HTTP 200 on /web/database/manager, /web/database/list authenticates to postgres successfully.
## Symptom
Fresh Odoo 20 deploy served `127.0.0.1:8069` only — Traefik and the swarm VIP got `connection refused`, preview domain returned HTTP 502.
## Root cause (`odoo/tools/config.py`)
- `--http-interface` defaults to `127.0.0.1` (line 289)
- an empty `http_interface` is **force-reset** to `127.0.0.1` (lines 768-770)
- legacy `xmlrpc_port` key no longer exists (renamed `http_port`) — old conf line was silently ignored, port worked only via the 8069 default
## Fix
Generated `odoo.conf` now sets `http_interface = 0.0.0.0` + `http_port = 8069` (deploy.py, init-odoo.sh, inline.Dockerfile + README note).
## Verification
End-to-end on the live onebspace deployment: container now listens on `0.0.0.0:8069`, preview domain returns HTTP 200 on `/web/database/manager`, `/web/database/list` authenticates to postgres successfully.
Symptom: fresh Odoo 20 deploy serves 127.0.0.1:8069 only; Traefik and the
swarm VIP get connection refused -> HTTP 502 through the preview domain.
Root cause (odoo/tools/config.py):
- line 289: --http-interface my_default='127.0.0.1'
- lines 768-770: empty http_interface is force-reset to 127.0.0.1
- the legacy xmlrpc_port key no longer exists (renamed http_port), so
the old conf line was silently ignored (port worked only via default)
Fix: generated odoo.conf now sets http_interface = 0.0.0.0 and
http_port = 8069. Verified end-to-end on the onebspace deployment:
internal 8069 binds 0.0.0.0, preview domain returns 200.
Odoo 20's requirements.txt no longer ships the inotify python package,
so --dev=reload logged "'inotify' module not installed. Code autoreload
feature is disabled" and never restarted on file edits — breaking the
core promise of this blueprint (live edits auto-apply).
The init script now pip-installs inotify unconditionally after the
requirements install (cheap no-op when already present).
You are not authorized to merge this pull request.
This pull request can be merged automatically.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Symptom
Fresh Odoo 20 deploy served
127.0.0.1:8069only — Traefik and the swarm VIP gotconnection refused, preview domain returned HTTP 502.Root cause (
odoo/tools/config.py)--http-interfacedefaults to127.0.0.1(line 289)http_interfaceis force-reset to127.0.0.1(lines 768-770)xmlrpc_portkey no longer exists (renamedhttp_port) — old conf line was silently ignored, port worked only via the 8069 defaultFix
Generated
odoo.confnow setshttp_interface = 0.0.0.0+http_port = 8069(deploy.py, init-odoo.sh, inline.Dockerfile + README note).Verification
End-to-end on the live onebspace deployment: container now listens on
0.0.0.0:8069, preview domain returns HTTP 200 on/web/database/manager,/web/database/listauthenticates to postgres successfully.Symptom: fresh Odoo 20 deploy serves 127.0.0.1:8069 only; Traefik and the swarm VIP get connection refused -> HTTP 502 through the preview domain. Root cause (odoo/tools/config.py): - line 289: --http-interface my_default='127.0.0.1' - lines 768-770: empty http_interface is force-reset to 127.0.0.1 - the legacy xmlrpc_port key no longer exists (renamed http_port), so the old conf line was silently ignored (port worked only via default) Fix: generated odoo.conf now sets http_interface = 0.0.0.0 and http_port = 8069. Verified end-to-end on the onebspace deployment: internal 8069 binds 0.0.0.0, preview domain returns 200.View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.