From d28cfed3c7d2311940309ee4015700e5a92abd5e Mon Sep 17 00:00:00 2001 From: rcourtman Date: Wed, 5 Nov 2025 23:05:47 +0000 Subject: [PATCH] Improve temperature monitoring setup messaging for containerized deployments When Pulse is running in a container and the SSH key is not available, provide clearer guidance about the pulse-sensor-proxy requirement and include documentation link for Docker deployments. This helps users understand that containerized Pulse needs the host-side sensor proxy to access temperature data from Proxmox hosts. --- internal/api/config_handlers.go | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/internal/api/config_handlers.go b/internal/api/config_handlers.go index 8b373fd..c3cf69c 100644 --- a/internal/api/config_handlers.go +++ b/internal/api/config_handlers.go @@ -4409,7 +4409,15 @@ Host ${NODE} else echo "" echo "⚠️ SSH key not available from Pulse server" - echo " Temperature monitoring cannot be configured automatically" + if [ "$PULSE_IS_CONTAINERIZED" = true ]; then + echo " Pulse is running in a container, so host-side temperature proxy is required." + echo " Install pulse-sensor-proxy on the Proxmox host and bind-mount /run/pulse-sensor-proxy into the container." + echo " After the proxy is online, rerun this setup script to push the SSH key." + echo " Docs: https://github.com/rcourtman/Pulse/blob/main/docs/TEMPERATURE_MONITORING.md#quick-start-for-docker-deployments" + else + echo " Temperature monitoring cannot be configured automatically." + echo " Ensure the Pulse service user has generated SSH keys and rerun this step." + fi fi else echo "Temperature monitoring skipped."