Release notification: the event ovhost announce publishes is host.release.published (its own type in openvibe-contracts 0.58.0; host.deploy.activated stays tenant hosting's), in the deploy script's comment and the README. Comments only (WS-P task 9)

OP OpenVibers committed 26 Sept 2026 · 4701423bca · 2 files, +2 −2

Changes

ddiff --git a/README.md b/README.md
iindex a1a87c5..01bc544 100644
---- a/README.md
++++ b/README.md
@@@ -41,7 +41,7 @@ the vhosts into `/etc/nginx/sites-available`, enables them and reloads nginx. Ea
  Let's Encrypt wildcard certificate (`certbot --dns-cloudflare`, see the host's renewal configs).
  Then, for each placeholder, it runs `ovhost announce <service> --release <id> --origin https://<domain>`
  with the service and release id from that placeholder's `release.json`. OpenVibe.Host publishes each release once, as
--`host.deploy.activated`, and open tabs check `/release.json` within seconds (WS-P task 9). This is best
++`host.release.published`, and open tabs check `/release.json` within seconds (WS-P task 9). This is best
  effort: it is skipped without an `ovhost` that has `announce`, stops at the first failure, and never fails the deploy.
  
  When a domain becomes a real app, delete it from `sites.json`, remove its vhost, and point the
ddiff --git a/deploy/scripts/deploy.sh b/deploy/scripts/deploy.sh
iindex 6e51be6..522c550 100755
---- a/deploy/scripts/deploy.sh
++++ b/deploy/scripts/deploy.sh
@@@ -17,7 +17,7 @@ if [ "$changed" = 1 ]; then sudo nginx -t && sudo systemctl reload nginx && echo
  echo "[sites] $(ls dist | wc -l) sites in place"
  # Release notifications (roadmap WS-P task 9): one `ovhost announce <service> --release <id> --origin
  # https://<domain>` per placeholder, from its dist/<domain>/release.json. OpenVibe.Host publishes
--# host.deploy.activated and open tabs check /release.json now instead of at their next poll; ovhost sends a
++# host.release.published and open tabs check /release.json now instead of at their next poll; ovhost sends a
  # release once, so an unchanged placeholder sends nothing. Best effort: skipped without an ovhost whose
  # --help has `announce <service>`, 20 s at most each, stops at the first failure (the rest would fail the
  # same way), and never fails the deploy (OpenVibe.Host docs/release-notifications.md).

diff --git a/README.md b/README.md

index a1a87c5..01bc544 100644

--- a/README.md

+++ b/README.md

@@ -41,7 +41,7 @@ the vhosts into `/etc/nginx/sites-available`, enables them and reloads nginx. Ea

Let's Encrypt wildcard certificate (`certbot --dns-cloudflare`, see the host's renewal configs).

Then, for each placeholder, it runs `ovhost announce <service> --release <id> --origin https://<domain>`

with the service and release id from that placeholder's `release.json`. OpenVibe.Host publishes each release once, as

-`host.deploy.activated`, and open tabs check `/release.json` within seconds (WS-P task 9). This is best

+`host.release.published`, and open tabs check `/release.json` within seconds (WS-P task 9). This is best

effort: it is skipped without an `ovhost` that has `announce`, stops at the first failure, and never fails the deploy.

When a domain becomes a real app, delete it from `sites.json`, remove its vhost, and point the

diff --git a/deploy/scripts/deploy.sh b/deploy/scripts/deploy.sh

index 6e51be6..522c550 100755

--- a/deploy/scripts/deploy.sh

+++ b/deploy/scripts/deploy.sh

@@ -17,7 +17,7 @@ if [ "$changed" = 1 ]; then sudo nginx -t && sudo systemctl reload nginx && echo

echo "[sites] $(ls dist | wc -l) sites in place"

# Release notifications (roadmap WS-P task 9): one `ovhost announce <service> --release <id> --origin

# https://<domain>` per placeholder, from its dist/<domain>/release.json. OpenVibe.Host publishes

-# host.deploy.activated and open tabs check /release.json now instead of at their next poll; ovhost sends a

+# host.release.published and open tabs check /release.json now instead of at their next poll; ovhost sends a

# release once, so an unchanged placeholder sends nothing. Best effort: skipped without an ovhost whose

# --help has `announce <service>`, 20 s at most each, stops at the first failure (the rest would fail the

# same way), and never fails the deploy (OpenVibe.Host docs/release-notifications.md).