From aa35f2149a2c4037f858bda6d6c1d088964e296d Mon Sep 17 00:00:00 2001 From: Brice TEXIER Date: Mon, 9 Nov 2026 10:15:13 +0100 Subject: [PATCH] =?UTF-8?q?D=C3=A9crire=20dans=20le=20README=20les=20hooks?= =?UTF-8?q?=20r=C3=A9ellement=20enregistr=C3=A9s?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit La section Usage disait que le plugin lance solid_queue:restart après le déploiement. register_hooks enregistre en fait quiet après deploy:starting, stop après deploy:updated, start après deploy:published et restart seulement après deploy:failed. quiet envoie SIGTERM, auquel Solid Queue 1.7.2 répond par un arrêt propre (supervisor/signals.rb). Co-Authored-By: Claude Opus 5.5 --- README.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 42a7336..1c23536 100644 --- a/README.md +++ b/README.md @@ -67,7 +67,13 @@ through their Capistrano counterparts, ex: `bundle exec cap solid_queue:restart` ## Usage -The plugin has registered a Capistrano `hook` to run `bundle exec cap solid_queue:restart` after deploy. +The plugin registers these Capistrano hooks: + +- after `deploy:starting`, `solid_queue:quiet` sends `SIGTERM` to the service, so Solid Queue starts a graceful shutdown; +- after `deploy:updated`, `solid_queue:stop` stops the service; +- after `deploy:published`, `solid_queue:start` starts the service on the new release; +- after `deploy:failed`, `solid_queue:restart` restarts the service. + See [`#register_hooks`](lib/capistrano/solid_queue.rb) ## Development