openvibers/openvibe.host Commits

Point Host runbook principal commands at network.env and --write-env (#12)

OP OpenVibers committed 3 Oct 2026 · e474593fd1 · 2 files, +4 −4

checks run by GitHub CI (test, test-pg) · CI ✓ 3/3 · review SHIP by DeepSeek harness

https://github.com/OpenVibers/OpenVibe.Host/pull/12

Changes

ddiff --git a/docs/developer-path.md b/docs/developer-path.md
iindex 8ec62a4..158dd41 100644
---- a/docs/developer-path.md
++++ b/docs/developer-path.md
@@@ -53,7 +53,7 @@ copied to Media.
  Install (once, as root, in `/opt/openvibe.network`, then here):
  
  ```sh
--node server/setup/service-principal.js create probe --env-file /etc/openvibe/probe.env   # secret never printed
++node --env-file=/etc/openvibe/network.env server/setup/service-principal.js create probe --write-env /etc/openvibe/probe.env   # secret never printed
  systemctl restart openvibe-network        # seeds probe's default grants
  install -m 644 deploy/systemd/openvibe-toolsjob.{service,timer} /etc/systemd/system/ && systemctl daemon-reload
  systemctl enable --now openvibe-toolsjob.timer
ddiff --git a/docs/release-notifications.md b/docs/release-notifications.md
iindex 8b99aa1..9f9c3db 100644
---- a/docs/release-notifications.md
++++ b/docs/release-notifications.md
@@@ -79,11 +79,11 @@ All commands run on the production host. None of them prints a secret.
  
  1. **Is the `host` client there?** Network seeds it at boot, with a secret that only its database holds.
     ```
--   cd /opt/openvibe.network && sudo node server/setup/service-principal.js list | grep -E '^host\s'
++   cd /opt/openvibe.network && sudo node --env-file=/etc/openvibe/network.env server/setup/service-principal.js list | grep -E '^host\s'
     ```
     Expect `host	site	OpenVibe.Host`. It is listed as `site` because it has the dashboard's redirect
     URI; client_credentials works for it all the same. If the line is missing, create the client instead of rotating it in step 2:
--   `sudo node server/setup/service-principal.js create host --env-file /etc/openvibe/host.env`.
++   `sudo node --env-file=/etc/openvibe/network.env server/setup/service-principal.js create host --write-env /etc/openvibe/host.env`.
  2. **Does Host's env file already hold its secret?** It does if the Host API was set up with one. The
     first command counts matching lines and never prints a value.
     ```
@@@ -91,7 +91,7 @@ All commands run on the production host. None of them prints a secret.
     ```
     If it prints `0`, or the file does not exist, write a fresh secret into it:
     ```
--   cd /opt/openvibe.network && sudo node server/setup/service-principal.js rotate host --env-file /etc/openvibe/host.env
++   cd /opt/openvibe.network && sudo node --env-file=/etc/openvibe/network.env server/setup/service-principal.js rotate host --write-env /etc/openvibe/host.env
     sudo systemctl restart openvibe-host
     ```
     Rotating changes the secret the running Host API uses, so restart it afterwards. The script writes