From 3eafcd80014f36b252e51f54eeed0fee7426e917 Mon Sep 17 00:00:00 2001
From: "courtmanr@gmail.com" <courtmanr@gmail.com>
Date: Wed, 23 Apr 2025 15:12:05 +0100
Subject: [PATCH] refactor: Replace pulse-proxmox branding with pulse-monitor

---
 README.md                | 16 ++++++++++------
 scripts/install-pulse.sh |  8 ++++----
 2 files changed, 14 insertions(+), 10 deletions(-)

diff --git a/README.md b/README.md
index bc5b8bba6..7638a0b1e 100644
--- a/README.md
+++ b/README.md
@@ -186,7 +186,7 @@ For installation within a Proxmox VE LXC container, a convenient script is provi
     *   It will guide you through creating the required Proxmox API Token if needed.
     *   It will ask for your Proxmox Host URL, API Token ID, and API Token Secret.
     *   It will ask about allowing self-signed certificates and optionally setting a custom port.
-    *   It will configure Pulse and set it up as a `systemd` service (`pulse-proxmox.service`) to run automatically.
+    *   It will configure Pulse and set it up as a `systemd` service (`pulse-monitor.service`) to run automatically.
     *   **Automatic Updates (Optional):** After a successful installation or update, the script will ask if you want to enable automatic updates (Daily, Weekly, or Monthly) via a cron job.
 
 4.  **Access Pulse:** Once the script finishes, it will display the URL (using the LXC's IP address) where you can access the Pulse dashboard (e.g., `http://<LXC-IP-ADDRESS>:7655`).
@@ -216,12 +216,16 @@ If you enable automatic updates via the script prompt:
 - Output (including any errors) from the update process is logged to `/var/log/pulse_update.log`.
 - You can view the root crontab using `sudo crontab -l -u root` and edit it using `sudo crontab -e -u root`.
 
-**Managing the Service (inside LXC):**
+**Managing the Pulse Service**
 
-- **Check Status:** `sudo systemctl status pulse-proxmox.service`
-- **Stop Service:** `sudo systemctl stop pulse-proxmox.service`
-- **Start Service:** `sudo systemctl start pulse-proxmox.service`
-- **View Logs:** `sudo journalctl -u pulse-proxmox.service -f`
+Once installed, the Pulse application runs as a `systemd` service. You can manage it using standard `systemctl` commands:
+
+*   **Check Status:** `sudo systemctl status pulse-monitor.service`
+*   **Stop Service:** `sudo systemctl stop pulse-monitor.service`
+*   **Start Service:** `sudo systemctl start pulse-monitor.service`
+*   **View Logs:** `sudo journalctl -u pulse-monitor.service -f`
+*   **Enable on Boot (usually done by script):** `sudo systemctl enable pulse-monitor.service`
+*   **Disable on Boot:** `sudo systemctl disable pulse-monitor.service`
 
 ## ✨ Features
 
diff --git a/scripts/install-pulse.sh b/scripts/install-pulse.sh
index b3e02148a..7f02e1fd6 100644
--- a/scripts/install-pulse.sh
+++ b/scripts/install-pulse.sh
@@ -7,9 +7,9 @@ set -euo pipefail
 
 # --- Configuration ---
 NODE_MAJOR_VERSION=${NODE_MAJOR_VERSION:-20}
-PULSE_DIR="${PULSE_DIR:-/opt/pulse-proxmox}"
+PULSE_DIR="${PULSE_DIR:-/opt/pulse-monitor}"
 PULSE_USER="${PULSE_USER:-pulse}"
-SERVICE_NAME="${SERVICE_NAME:-pulse-proxmox.service}"
+SERVICE_NAME="${SERVICE_NAME:-pulse-monitor.service}"
 SCRIPT_NAME="install-pulse.sh"
 LOG_FILE="/var/log/pulse_update.log"
 CRON_IDENTIFIER="# Pulse-Auto-Update ($SCRIPT_NAME)"
@@ -489,7 +489,7 @@ setup_systemd_service() {
   print_info "Creating service file at $service_file..."
   cat << EOF > "$service_file"
 [Unit]
-Description=Pulse for Proxmox VE Monitoring Application
+Description=Pulse Monitoring Application
 After=network.target
 
 [Service]
@@ -666,7 +666,7 @@ final_instructions() {
     port_value="7655"
   fi
   echo ""
-  print_success "Pulse for Proxmox VE installation and setup complete!"
+  print_success "Pulse installation and setup complete!"
   echo "-------------------------------------------------------------"
   print_info "You should be able to access the Pulse dashboard at:"
   if [ -n "$ip_address" ]; then