From e9b532ccd8c3f242bfa0e35762f9351c6f3a542c Mon Sep 17 00:00:00 2001 From: Louis Lam Date: Thu, 23 Jun 2022 16:16:11 +0800 Subject: [PATCH 1/5] Update to 1.17.1 --- πŸ†™-How-to-Update.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/πŸ†™-How-to-Update.md b/πŸ†™-How-to-Update.md index 6342075..d4770d6 100644 --- a/πŸ†™-How-to-Update.md +++ b/πŸ†™-How-to-Update.md @@ -34,7 +34,7 @@ cd # Update from git git fetch --all -git checkout 1.17.0 --force +git checkout 1.17.1 --force # Install dependencies and prebuilt npm install --production From e983952325ac9bbfc3a97a80265d7adc42fec9bc Mon Sep 17 00:00:00 2001 From: Louis Lam Date: Thu, 30 Jun 2022 16:39:37 +0800 Subject: [PATCH 2/5] Created Troubleshooting (markdown) --- Troubleshooting.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 Troubleshooting.md diff --git a/Troubleshooting.md b/Troubleshooting.md new file mode 100644 index 0000000..75552b8 --- /dev/null +++ b/Troubleshooting.md @@ -0,0 +1,16 @@ + +## Uptime Kuma reports DOWN, but I can access. + +If your Uptime Kuma reports DOWN of your service, sometimes you would like to know it is a bug of Uptime Kuma or your own Docker network issue. + +Go into your container's bash. + +``` +docker exec -it uptime-kuma bash +``` + +Then you can test with these commands for example: +``` +curl https://google.com +ping google.com +``` From 870aba5aef1a2cd2f33f3fdf4658be059ee0455e Mon Sep 17 00:00:00 2001 From: K3rnelPan1c <69395733+k3rnelpan1c-dev@users.noreply.github.com> Date: Fri, 8 Jul 2022 17:10:09 +0200 Subject: [PATCH 3/5] add: unofficial rootless Helm 3 Chart --- πŸ”§-How-to-Install.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/πŸ”§-How-to-Install.md b/πŸ”§-How-to-Install.md index 5685f66..68946a5 100644 --- a/πŸ”§-How-to-Install.md +++ b/πŸ”§-How-to-Install.md @@ -132,6 +132,15 @@ https://github.com/louislam/uptime-kuma/wiki/Reverse-Proxy See more [here](https://github.com/louislam/uptime-kuma/tree/k8s-unofficial/kubernetes) +### ☸️ OpenShift 4 and Kubernetes Helm 3 Chart (Unofficial) + +> Note: This Chart relies on a repackaged OCI Container Image, which lets *uptime-kuma* run as **non-root** user. \ +> The entire repackage process is automated via GitHub Actions and renovate-bot keeps everything up to date. (feel free to audit it yourself) + +The Containerfile used to rebundle *uptime-kuma*: [rootless Containerfile](https://github.com/k3rnelpan1c-dev/uptime-kuma-helm/blob/main/container/Containerfile) + +https://github.com/k3rnelpan1c-dev/uptime-kuma-helm + ### Ansible (Unofficial) https://github.com/louislam/uptime-kuma/tree/ansible-unofficial/ansible From fc5b5f85cf8f6b1ae90cd2148c2e4828fe731433 Mon Sep 17 00:00:00 2001 From: seppe peeters Date: Mon, 22 Aug 2022 16:31:27 +0200 Subject: [PATCH 4/5] Update Reverse-Proxy.md hi, tnx for this great tool. very useful! above fixed websocket connection for old Apache. ( https://stackoverflow.com/questions/53939609/apache-websocket-connectionupgrade-replaced-by-keep-alive helped. ) --- Reverse-Proxy.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/Reverse-Proxy.md b/Reverse-Proxy.md index ca5e24c..4dfecc5 100644 --- a/Reverse-Proxy.md +++ b/Reverse-Proxy.md @@ -69,9 +69,10 @@ With SSL: ProxyPass / http://localhost:3001/ RewriteEngine on - RewriteCond %{HTTP:Upgrade} websocket [NC] - RewriteCond %{HTTP:Connection} upgrade [NC] - RewriteRule ^/?(.*) "ws://localhost:3001/$1" [P,L] + RewriteCond %{HTTP:Upgrade} =websocket + RewriteRule /(.*) ws://localhost:3001/$1 [P,L] + RewriteCond %{HTTP:Upgrade} !=websocket + RewriteRule /(.*) http://localhost:3001/$1 [P,L] ``` From 93440d03fda91dab409fbfb95bfe92b457948326 Mon Sep 17 00:00:00 2001 From: Raymond Hackley Date: Tue, 6 Sep 2022 22:13:51 +0000 Subject: [PATCH 5/5] Add OpenRC-Script.md --- OpenRC-Script.md | 66 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 66 insertions(+) create mode 100644 OpenRC-Script.md diff --git a/OpenRC-Script.md b/OpenRC-Script.md new file mode 100644 index 0000000..5799ba6 --- /dev/null +++ b/OpenRC-Script.md @@ -0,0 +1,66 @@ +For Alpine/postmarketOS/Gentoo/Artix, you can create an OpenRC service as +`/etc/init.d/uptime-kuma`: + +```sh +#!/sbin/openrc-run + +description="Uptime Kuma self-hosted monitoring tool" + +# Change $directory to path to uptime-kuma +directory=${directory:-/usr/share/uptime-kuma} +pidfile=${pidfile:-/run/$RC_SVCNAME.pid} + +log_dir="/var/log/$RC_SVCNAME" +output_log="${output_log:-$log_dir/output.log}" +error_log="${error_log:-$log_dir/error.log}" + +command=${command:-/usr/bin/node} +command_args="$directory/server/server.js" +command_user=${command_user:-uptime-kuma:uptime-kuma} +command_background=true + +depend() { + need net +} + +start_pre() { + checkpath --owner=$command_user --directory $log_dir \ + $directory/data \ + $directory/data/upload + checkpath --owner=$command_user --file $log_dir/*.log \ + $directory/data/error.log \ + $directory/data/kuma.db +} + +start_post() { + # Wait for the server to be started + sleep 10 +} +``` + +Set the script to executable. + +```sh +sudo chmod 755 /etc/init.d/uptime-kuma +``` + +Create a user and group `uptime-kuma:uptime-kuma` for the service. + +```sh +sudo addgroup -S uptime-kuma +sudo adduser -S -D -h /var/lib/uptime-kuma -s /sbin/nologin -G uptime-kuma -g uptime-kuma uptime-kuma +``` + +If the database is not initialized, it has to be run fisrt. + +```sh +cd /usr/share/uptime-kuma +sudo -u uptime-kuma node server/server.js +``` + +Start the service and add it to default runlevel if prefered. + +```sh +sudo rc-service uptime-kuma start +sudo rc-update add uptime-kuma +```