RPi-Monitor Revival
After a long pause I decided to restart working on RPi-Monitor with the assistance of AI.
AI Assisted development can be something very efficient and will allow me to deliver fast and reliables updates to the project.
Actually, I'm using free token provided by Mistral-Vibe, Codex, Gemini and Cursor and I run quite quickly out of token. So the development don't go as fast as it could.
You like this project? You can participate by giving a tip on my Ko-fi as soon as enough money will be collected, I will subscribe to an AI plan giving me more token to use for the development of RPi-Monitor.
RPi-Monitor remain free and I don't ask funding for the time I spend doing the development.
What will come next ?
- New installation process based on an install script - already published
- New documentation based on mdbook
- New set of tests to validate RPi-Monitor bahavior and ensure quick release
- Review of each remaining issue and PR
- Theses steps are the fundation of new features and a wider compatibility (Not only debian based distro but any Linux). My overall objective is to port this software to Rust ... but this will not occurs without AI assistance...
Overview
RPi-Monitor is an application designed to perform real time monitoring Linux devices. It has initially been designed to run on a Raspberry Pi B.
RPi-Monitor provides a lot of feature such as Embedded Web server, Alert messaging, SNMP integration...
For details, refer to keys features of RPi-Monitor in documentation.
Screenshots
See Screenshots chapter of documentation to see more screenshots.
Installation
Quick installation
RPi-Monitor can be installed or updated directly from the command line using the installation script. The script downloads the appropriate release from GitHub, verifies its SHA-256 checksum, and installs or updates RPi-Monitor.
On supported Debian-based systems, run:
curl -fsSL https://raw.githubusercontent.com/RPi-Monitor/RPi-Monitor/main/install.sh | sudo bashThis command downloads and executes the installation script without requiring a manual download.
Requirements:
- A supported Debian-based system: Debian, Raspberry Pi OS (Raspbian), or Ubuntu.
curl,jq, andunzip. The script checks for these tools and reports any missing dependencies.- Root privileges, provided here by
sudo. - An interactive terminal to confirm the installation, unless
--yesis specified.
Important: The script must be executed with Bash. Do not replacebashwithsh, as the script uses Bash-specific syntax. The script also refuses to run if RPi-Monitor is still installed through the Debian package; remove that package first withsudo apt remove rpimonitor. Your configuration in/etc/rpimonitoris kept... but doing a backup first is always a good idea.
Show all installation options
Installation options
The installation script supports options to select a release, automate confirmation, simulate an installation, and customize service management.
The options can be passed after the script URL by using bash -s --:
curl -fsSL https://raw.githubusercontent.com/RPi-Monitor/RPi-Monitor/main/install.sh | sudo bash -s -- --helpAvailable options
| Option | Description |
| ------------------- | ------------------------------------------------------------------------------------------------------------ |
| -h, --help | Display the available options and exit. |
| -y, --yes | Automatically confirm the operation. Required when running without an interactive terminal. |
| --version VERSION | Install a specific published release, for example --version 2.14. The optional leading v is accepted. |
| --pre-release | Select the newest published release, including pre-releases. Pre-releases may not be stable. |
| --force | Force installation or reinstallation even if the installed version is already up to date. |
| --dry-run | Simulate the installation or update without applying the system changes. Root privileges are still required. |
| --no-service | Skip systemd service management. The script will not enable, start, or restart the service. |
Examples
Install the latest stable release and confirm interactively:
curl -fsSL https://raw.githubusercontent.com/RPi-Monitor/RPi-Monitor/main/install.sh | sudo bashInstall a specific release:
curl -fsSL https://raw.githubusercontent.com/RPi-Monitor/RPi-Monitor/main/install.sh | sudo bash -s -- --version 2.14Install the newest release, including pre-releases:
curl -fsSL https://raw.githubusercontent.com/RPi-Monitor/RPi-Monitor/main/install.sh | sudo bash -s -- --pre-releaseRun without an interactive confirmation:
curl -fsSL https://raw.githubusercontent.com/RPi-Monitor/RPi-Monitor/main/install.sh | sudo bash -s -- --yesSimulate an installation or update:
curl -fsSL https://raw.githubusercontent.com/RPi-Monitor/RPi-Monitor/main/install.sh | sudo bash -s -- --dry-runForce reinstallation of the current version:
curl -fsSL https://raw.githubusercontent.com/RPi-Monitor/RPi-Monitor/main/install.sh | sudo bash -s -- --forceInstall without managing the systemd service:
curl -fsSL https://raw.githubusercontent.com/RPi-Monitor/RPi-Monitor/main/install.sh | sudo bash -s -- --no-serviceOptions can be combined. For example, to install a specific version automatically without managing the service:
curl -fsSL https://raw.githubusercontent.com/RPi-Monitor/RPi-Monitor/main/install.sh | sudo bash -s -- --version 2.14 --yes --no-serviceCustom deployment root
The TARGET_DIR environment variable allows the files to be deployed under an alternative root directory. This is useful for testing or preparing a filesystem image.
For example:
sudo TARGET_DIR=/tmp/rpi-root bash ./install.sh --dry-runNote: TARGET_DIR changes the destination of deployed files, but does not isolate system-level operations such as package management. Use it with care.
Documentation
If you want to install, use or customize RPi-Monitor refer to documentation
If you want to see example of configuration and see what RPi-Monitor can do, refer to RPi-Monitor Usages.
Frequently Asked Question find answer into the FAQ page.
Development
If you want to participate and propose a pull request, refer to contributing chapter of documentation.
Note: Pull request perfomed on develop branch will be integrated as soon as possible. Pull request perform on master branche may only be integrated when a new version is published (or not may not be integrated at all...)
License
License: GPLv3