ilot/uptime-kuma: new aport

ilot/uptime-kuma/uptime-kuma.conf

@@ -0,0 +1,47 @@
+# uptime-kuma config
+# for more info
+# see https://github.com/louislam/uptime-kuma/wiki/Environment-Variables
+
+# Set the directory where the data should be stored (could be relative)
+# DATA_DIR=/var/lib/uptime-kuma
+
+# Host to bind to, could be an ip.
+# UPTIME_KUMA_HOST=::
+
+# Port to listen to
+# UPTIME_KUMA_PORT=3001
+
+# Path to SSL key
+# UPTIME_KUMA_SSL_KEY=
+
+# Path to SSL certificate
+# UPTIME_KUMA_SSL_CERT=
+
+# SSL Key Passphrase
+# UPTIME_KUMA_SSL_KEY_PASSPHRASE=
+
+# Cloudflare Tunnel Token
+# UPTIME_KUMA_CLOUDFLARED_TOKEN=
+
+# By default, Uptime Kuma is not allowed in iframe if the domain name is not
+# the same as the parent. It protects your Uptime Kuma to be a phishing
+# website. If you don't need this protection, you can set it to true
+# UPTIME_KUMA_DISABLE_FRAME_SAMEORIGIN=false
+
+# By default, Uptime Kuma is verifying that the websockets ORIGIN-Header
+# matches your servers hostname. If you don't need this protection, you can
+# set it to bypass. See GHSA-mj22-23ff-2hrr for further context.
+# UPTIME_KUMA_WS_ORIGIN_CHECK=cors-like
+
+# Allow to specify any executables as Chromium
+# UPTIME_KUMA_ALLOW_ALL_CHROME_EXEC=0
+
+# Add your self-signed ca certs.
+# NODE_EXTRA_CA_CERTS=
+
+# Ignore all TLS errors
+# NOTE_TLS_REJECT_UNAUTHORIZED=0
+
+# Set it to --insecure-http-parser, if you encountered error Invalid header
+# value char when your website using WAF
+# NODE_OPTIONS=