Add Uptime Kuma - A fancy self-hosted monitoring tool #7888
Conversation
MichaIng
left a comment
MichaIng
left a comment
There was a problem hiding this comment.
Great stuff, there is an open request for this as well. Some points below.
…) via Download_Install(). Do not exec 'npm run setup' anymore, since the install script uses git to checkout latest repo. We pull the latest release anyway. Use only npm commands for installation. Added hardening to system service. Minimized db-config. Removed unecessary aSTART_SERVICES, added service name to To_Install instead.
…/dietpi_userdata/uptime-kuma are presevered when uninstalling the app
MichaIng
force-pushed
the
feature/add-uptime-kuma
branch
from
78934bc to
3d41414
Compare
* Aligned latest release tag capture with other software options: Pull the latest stable only, no beta versions or non-release tags. Use a fallback version in case check fails or repo structure changes. * Do npm setup steps in tmpfs for theoretical speedup, and remove old instance only after this succeeded. * Limit systemd service restart loops and start after network-online target. * Offer to remove userdata as well on uninstall * Check for GitHub API URL and update fallback tag with our CI workflow * Add dietpi-survey support, changelog, and README entry * Align indentation
|
I hope the EDIT: It does not seem to support RISC-V. It tries to find a local module, which does not exist, then tries to download it, where it does not exist either for this architecture: https://github.com/louislam/node-sqlite3/releases |
MichaIng
changed the title
|
Important wiki page: https://github.com/louislam/uptime-kuma/wiki/Environment-Variables So we can change the port to 3002 (3001 conflicts with Grafana) and set the data dir directly, i.e. no need for the symlink. Also EDIT: Port added to our wiki page already, so we won't forget it. EDIT2: Ah, switching back to stable releases caused this version mismatch issue you mentioned. The wider problem of this is that the |
to avoid conflict with Grafana. Also add service and port test to our CI, work around false v2.0.1 string in 2.0.2 code, set data dir via CLI arg, assign more meaningful syslog identifier (than "node") and skip redundant NODE_ENV, which defaults to "production" anyway.
MichaIng
force-pushed
the
feature/add-uptime-kuma
branch
from
ed0a9b4 to
994b8ff
Compare
MichaIng
left a comment
MichaIng
left a comment
There was a problem hiding this comment.
Looks and runs great for me now. Will merge, @JappeHallunken let me know if I overlooked and messed something up with my last commits 😅.
|
Yes, looks good to me! |
https://github.com/louislam/uptime-kuma
@StephanStS mailed me about this a few days ago and it looks pretty nice. It's a web dashboard where you can add your self-hosted services (or you could also monitor external services, basically everything that's accessible via the internet).
In the current form it just runs on it's own port, I did not add any webserver integrations / reversy proxy configs.
It's also a bit of a hassle to run it from a subpath, officially it's not supported, see: louislam/uptime-kuma#147
I think most DietPi users will run not their own domain, most likely they run it locally or they have a DynDNS domain, so for running it on a subdomain another DynDNS domain would be necessary.
We could simply add proxy configuration notes to the software documentation or link to the Uptime Kuma docs, and avoid providing integration via dietpi-software, since it can run standalone and does not require a web server or reverse proxy for its core functionality.