secubox-deb/packages/secubox-metablogizer/api/routers
CyberMind-FR c838b83d17 fix(publish): delegate vhost/WAF/cert to metablogizer /publish/route; drop illegal root-config writes
secubox-publish's infra provisioner ran as unprivileged `secubox` and tried
to write /etc/nginx/sites-available/<domain>.conf, rewrite
/etc/haproxy/haproxy.cfg, write /etc/secubox/waf/haproxy-routes.json, and
reload nginx/haproxy/secubox-waf directly. All of these silently failed
(permission denied), which was the root cause of published sites answering
421/never routing. Metablogizer already owns routing through the audited
secubox-publishctl root helper (apply_route + provision_cert), so add a
POST /publish/route endpoint there and have the hub call it instead of
touching root config itself.

Co-Authored-By: Gerald KERMA <devel@cybermind.fr>
2026-07-11 13:28:32 +02:00
..
__init__.py feat(metablogizer): publisher wizard endpoints (wizard/export/import) 2026-07-11 13:14:40 +02:00
publish.py fix(publish): delegate vhost/WAF/cert to metablogizer /publish/route; drop illegal root-config writes 2026-07-11 13:28:32 +02:00