docs: add requirements.txt and explain why no Docker support

Author: m4r1k

CHANGELOG.md

@@ -13,20 +13,43 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - **Native Package Distribution:** Official `.deb` and `.rpm` packages for easy installation
 - **APT/DNF Repository:** Packages available via GitHub Pages hosted repository for Debian, Ubuntu, RHEL, and Fedora
 - **Version CLI Option:** New `-v`/`--version` flag to display current version
-- **Version Display:** Version now shown at service startup and during config validation
+- **Version Display:** Version now shown at service startup and in notifications
 - **nFPM Build System:** Automated package building using nFPM for both Debian and RPM formats
 - **GitHub Release Automation:** Packages automatically built and published on GitHub releases
-- **GPG Signed Packages:** All repository metadata is GPG signed for security
+- **GPG Signed Repository:** Repository metadata is GPG signed for security
+- **requirements.txt:** Added for pip-based installations (`PyYAML>=5.4.1`, `apprise>=1.9.6`)
+- **No Docker Documentation:** Explained why Eneru runs as a systemd daemon (chicken-and-egg problem with container shutdown)
 
 ### Changed
+- **Service Name:** Renamed from `ups-monitor.service` to `eneru.service` to avoid conflict with nut-client's service
 - **Installation Method:** Package installation (deb/rpm) is now the recommended method
 - **Service Behavior:** Packages install but do not auto-enable or auto-start the service (config must be edited first)
 - **Config File Handling:** Package upgrades preserve existing `/etc/ups-monitor/config.yaml` (marked as conffile)
+- **Upgrade Behavior:** Smart detection ensures running service restarts on upgrade, stopped service stays stopped
 - **Service File Location:** Moved from `/etc/systemd/system/` to `/lib/systemd/system/` for proper package management
-- **`__version__` Variable:** Version now embedded in source code and updated at build time from git tags
 
 ### Fixed
 - **Discord Mention Prevention:** Added zero-width space after `@` symbols in notification messages to prevent Discord from interpreting UPS names (e.g., `[email protected]`) as user mentions
+- **APT Repository Structure:** Proper `dists/stable/main/binary-all/` hierarchy for Debian/Ubuntu compatibility
+- **RPM Repository GPG:** Fixed gpgcheck configuration (repo metadata signed, individual packages served over HTTPS)
+
+### Migration from v4.2
+
+If you installed manually, update your systemd service reference:
+```bash
+# Stop old service
+sudo systemctl stop ups-monitor.service
+sudo systemctl disable ups-monitor.service
+
+# Remove old service file
+sudo rm /etc/systemd/system/ups-monitor.service
+
+# Install new package (recommended) or copy new service file
+sudo cp eneru.service /etc/systemd/system/
+sudo systemctl daemon-reload
+sudo systemctl enable eneru.service
+sudo systemctl start eneru.service
+```
 
 ### Installation
 

README.md

@@ -62,6 +62,22 @@ Most UPS shutdown solutions are **single-system focused**. Eneru is designed for
 
 ---
 
+## 🤔 Why an Old-Fashioned Systemd Daemon? (No Docker)
+
+You might wonder why Eneru runs as a traditional systemd service instead of a container. This is intentional:
+
+**The Chicken-and-Egg Problem:** Eneru's job is to gracefully shut down Docker/Podman containers during power events. If Eneru itself ran inside a container, it would be stopped during its own shutdown sequence—potentially stalling the entire process and leaving the host in an undefined state.
+
+Running as a systemd daemon ensures:
+- **Eneru survives container shutdown** - It can orchestrate the full sequence without being killed
+- **Direct host access** - Native access to systemd, virsh, SSH, and filesystem operations
+- **Reliability** - No container runtime dependency that could fail during a power event
+- **Simplicity** - While it's technically possible to code Eneru to run inside a container (with careful self-exclusion logic during shutdown), this would significantly increase codebase complexity and still introduce the possibility that something goes wrong—leaving Eneru unable to complete its job
+
+This is the same reason critical infrastructure services like NUT itself run as system daemons, not containers.
+
+---
+
 ## Features
 
 ### High-Performance Monitoring

requirements.txt

@@ -0,0 +1,13 @@
+# Eneru - Python Dependencies
+#
+# Install with: pip install -r requirements.txt
+#
+# Note: For production use, prefer system packages (apt/dnf) over pip
+# to ensure proper integration with system Python and security updates.
+
+# Required
+PyYAML>=5.4.1
+
+# Optional - for notifications (100+ services via Apprise)
+# Remove this line if you don't need notifications
+apprise>=1.9.6