rcourtman
973f1f9866
When running install-sensor-proxy.sh on multiple nodes in a cluster, each installation was removing all existing pulse-managed-key entries before adding its own. This caused the following scenario: 1. Run script on node A: node A's key is added to all nodes 2. Run script on node B: node B's key replaces node A's key on all nodes 3. Result: node A's proxy can no longer SSH to other nodes The fix changes the behavior to: - Check if the specific SSH key already exists on the target - Only add the key if not present (idempotent) - Never remove existing pulse-managed-key entries This allows multiple sensor-proxy installations to coexist in a cluster, with each node's proxy key authorized on all nodes. Related to #738
Pulse
Real-time monitoring for Proxmox VE, Proxmox Mail Gateway, PBS, and Docker infrastructure.
🚀 Overview
Pulse is a modern, unified dashboard for your Proxmox and Docker estate. It consolidates metrics, logs, and alerts from Proxmox VE, Proxmox Backup Server, Proxmox Mail Gateway, and standalone Docker hosts into a single, beautiful interface.
Designed for homelabs, sysadmins, and MSPs who need a "single pane of glass" without the complexity of enterprise monitoring stacks.
✨ Features
- Unified Monitoring: View health and metrics for PVE, PBS, PMG, and Docker containers in one place.
- Smart Alerts: Get notified via Discord, Slack, Telegram, Email, and more when things go wrong (e.g., "VM down", "Storage full").
- Auto-Discovery: Automatically finds Proxmox nodes on your network.
- Secure by Design: Credentials encrypted at rest, no external dependencies, and strict API scoping.
- Backup Explorer: Visualize backup jobs and storage usage across your entire infrastructure.
- Privacy Focused: No telemetry, no phone-home, all data stays on your server.
- Lightweight: Built with Go and React, running as a single binary or container.
⚡ Quick Start
Option 1: Proxmox LXC (Recommended)
Run this one-liner on your Proxmox host to create a lightweight LXC container:
curl -fsSL https://github.com/rcourtman/Pulse/releases/latest/download/install.sh | bash
Option 2: Docker
docker run -d \
--name pulse \
-p 7655:7655 \
-v pulse_data:/data \
--restart unless-stopped \
rcourtman/pulse:latest
Access the dashboard at http://<your-ip>:7655.
📚 Documentation
- Installation Guide: Detailed instructions for Docker, Kubernetes, and bare metal.
- Configuration: Setup authentication, notifications, and advanced settings.
- Security: Learn about Pulse's security model and best practices.
- API Reference: Integrate Pulse with your own tools.
- Troubleshooting: Solutions to common issues.
❤️ Support Pulse Development
Pulse is maintained by one person. Sponsorships help cover the costs of the demo server, development tools, and domains. If Pulse saves you time, please consider supporting the project!
📄 License
MIT © Richard Courtman