Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .env.example
Original file line number Diff line number Diff line change
Expand Up @@ -183,6 +183,7 @@ SEARXNG_HOSTNAME=searxng.yourdomain.com
SUPABASE_HOSTNAME=supabase.yourdomain.com
WAHA_HOSTNAME=waha.yourdomain.com
WEAVIATE_HOSTNAME=weaviate.yourdomain.com
UPTIME_KUMA_HOSTNME=uptime-kuma.yourdomain.com

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

Correct the hostname variable typo (HOSTNME → HOSTNAME).

UPTIME_KUMA_HOSTNME won’t be read by components using UPTIME_KUMA_HOSTNAME, so host routing/config will break.

Suggested fix
-UPTIME_KUMA_HOSTNME=uptime-kuma.yourdomain.com
+UPTIME_KUMA_HOSTNAME=uptime-kuma.yourdomain.com

As per coding guidelines, all service hostnames must end with _HOSTNAME suffix.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
UPTIME_KUMA_HOSTNME=uptime-kuma.yourdomain.com
UPTIME_KUMA_HOSTNAME=uptime-kuma.yourdomain.com
🧰 Tools
🪛 dotenv-linter (4.0.0)

[warning] 186-186: [UnorderedKey] The UPTIME_KUMA_HOSTNME key should go before the USER_DOMAIN_NAME key

(UnorderedKey)

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.env.example at line 186, Fix the typo in the environment variable name by
renaming UPTIME_KUMA_HOSTNME to UPTIME_KUMA_HOSTNAME in the .env.example so
components that read UPTIME_KUMA_HOSTNAME will work; ensure the variable uses
the required `_HOSTNAME` suffix and update any references or documentation that
might mirror the misspelling.

⚠️ Potential issue | 🟠 Major

Add uptime-kuma to GOST_NO_PROXY.

Since this PR introduces a new service container, it must be added to the internal bypass list to avoid proxying intra-stack traffic.

Suggested fix
-GOST_NO_PROXY=localhost,127.0.0.0/8,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16,.local,appsmith,postgres,postgres:5432,redis,redis:6379,caddy,ollama,neo4j,qdrant,weaviate,clickhouse,minio,searxng,crawl4ai,gotenberg,langfuse-web,langfuse-worker,flowise,n8n,n8n-import,n8n-worker-1,n8n-worker-2,n8n-worker-3,n8n-worker-4,n8n-worker-5,n8n-worker-6,n8n-worker-7,n8n-worker-8,n8n-worker-9,n8n-worker-10,n8n-runner-1,n8n-runner-2,n8n-runner-3,n8n-runner-4,n8n-runner-5,n8n-runner-6,n8n-runner-7,n8n-runner-8,n8n-runner-9,n8n-runner-10,letta,lightrag,docling,postiz,temporal,temporal-ui,ragflow,ragflow-mysql,ragflow-minio,ragflow-redis,ragflow-elasticsearch,ragapp,open-webui,comfyui,waha,libretranslate,paddleocr,nocodb,db,studio,kong,auth,rest,realtime,storage,imgproxy,meta,functions,analytics,vector,supavisor,gost,api.telegram.org,telegram.org,t.me,core.telegram.org
+GOST_NO_PROXY=localhost,127.0.0.0/8,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16,.local,appsmith,postgres,postgres:5432,redis,redis:6379,caddy,ollama,neo4j,qdrant,weaviate,clickhouse,minio,searxng,crawl4ai,gotenberg,langfuse-web,langfuse-worker,flowise,n8n,n8n-import,n8n-worker-1,n8n-worker-2,n8n-worker-3,n8n-worker-4,n8n-worker-5,n8n-worker-6,n8n-worker-7,n8n-worker-8,n8n-worker-9,n8n-worker-10,n8n-runner-1,n8n-runner-2,n8n-runner-3,n8n-runner-4,n8n-runner-5,n8n-runner-6,n8n-runner-7,n8n-runner-8,n8n-runner-9,n8n-runner-10,letta,lightrag,docling,postiz,temporal,temporal-ui,ragflow,ragflow-mysql,ragflow-minio,ragflow-redis,ragflow-elasticsearch,ragapp,open-webui,comfyui,waha,libretranslate,paddleocr,nocodb,uptime-kuma,db,studio,kong,auth,rest,realtime,storage,imgproxy,meta,functions,analytics,vector,supavisor,gost,api.telegram.org,telegram.org,t.me,core.telegram.org

As per coding guidelines, all service container names must be listed in GOST_NO_PROXY in .env.example.

🧰 Tools
🪛 dotenv-linter (4.0.0)

[warning] 186-186: [UnorderedKey] The UPTIME_KUMA_HOSTNME key should go before the USER_DOMAIN_NAME key

(UnorderedKey)

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.env.example at line 186, The .env.example is missing the new service name
in the internal no-proxy list: update the GOST_NO_PROXY variable to include the
new container name "uptime-kuma" (matching the introduced UPTIME_KUMA_HOSTNME
entry) so intra-stack traffic is bypassed by the proxy; locate the GOST_NO_PROXY
definition in .env.example and append "uptime-kuma" to the comma/space-separated
list following the existing formatting/conventions.

WEBUI_HOSTNAME=webui.yourdomain.com
WELCOME_HOSTNAME=welcome.yourdomain.com

Expand Down
3 changes: 3 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,9 @@

## [Unreleased]

### Fixed
- **Uptime Kuma** - Self-hosted uptime monitoring with 90+ notification services

Comment on lines +5 to +7

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Move this entry from Fixed to Added.

Uptime Kuma is a new capability, so this should be documented under ### Added in [Unreleased].

As per coding guidelines, CHANGELOG entries should follow semantic categories (Added, Changed, Fixed).

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@CHANGELOG.md` around lines 5 - 7, Move the "Uptime Kuma - Self-hosted uptime
monitoring with 90+ notification services" changelog entry out of the "###
Fixed" section into the "### Added" section under the "[Unreleased]" heading;
specifically locate the line containing "Uptime Kuma" and cut it from the "###
Fixed" block and paste it into the "### Added" block so the entry is categorized
as a new capability rather than a fix.

## [1.3.3] - 2026-02-27

### Fixed
Expand Down
5 changes: 5 additions & 0 deletions Caddyfile
Original file line number Diff line number Diff line change
Expand Up @@ -107,6 +107,11 @@ import /etc/caddy/addons/tls-snippet.conf
reverse_proxy temporal-ui:8080
}

# Uptime Kuma
{$UPTIME_KUMA_HOSTNAME} {
reverse_proxy uptimekuma:3001
}
Comment on lines +110 to +113

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

Fix Uptime Kuma Caddy block: missing TLS import and wrong upstream hostname.

This block currently skips the shared TLS snippet and proxies to a non-existent upstream name.

Suggested fix
 # Uptime Kuma
 {$UPTIME_KUMA_HOSTNAME} {
-    reverse_proxy uptimekuma:3001
+    import service_tls
+    reverse_proxy uptime-kuma:3001
 }

Also ensure UPTIME_KUMA_HOSTNAME is passed into the caddy service environment in docker-compose.yml, otherwise this host matcher won’t resolve at runtime.

As per coding guidelines, all Caddyfile service blocks must use import service_tls for consistent TLS configuration.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
# Uptime Kuma
{$UPTIME_KUMA_HOSTNAME} {
reverse_proxy uptimekuma:3001
}
# Uptime Kuma
{$UPTIME_KUMA_HOSTNAME} {
import service_tls
reverse_proxy uptime-kuma:3001
}
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@Caddyfile` around lines 110 - 113, The Caddy site block for Uptime Kuma is
missing the shared TLS import and points to an incorrect upstream; update the
block that matches {$UPTIME_KUMA_HOSTNAME} to include "import service_tls" as
the first line and change the reverse_proxy target from "uptimekuma:3001" to the
correct container hostname (ensure it matches the service name used in
docker-compose), and also add UPTIME_KUMA_HOSTNAME to the caddy service
environment in docker-compose.yml so the host matcher resolves at runtime.


# Databasus
{$DATABASUS_HOSTNAME} {
import service_tls
Expand Down
2 changes: 2 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -112,6 +112,8 @@ The installer also makes the following powerful open-source tools **available fo

✅ [**Supabase**](https://supabase.com/) - An open-source alternative to Firebase, providing database storage, user authentication, and more. It's a popular choice for AI applications.

✅ [**Uptime Kuma**](https://github.com/louislam/uptime-kuma - Self-hosted uptime monitoring tool with notifications

Comment on lines +115 to +116

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Fix malformed Markdown link for Uptime Kuma.

The link is missing the closing ) and currently swallows the description text into the URL.

Suggested fix
-✅ [**Uptime Kuma**](https://github.com/louislam/uptime-kuma - Self-hosted uptime monitoring tool with notifications
+✅ [**Uptime Kuma**](https://github.com/louislam/uptime-kuma) - Self-hosted uptime monitoring tool with notifications
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
✅ [**Uptime Kuma**](https://github.com/louislam/uptime-kuma - Self-hosted uptime monitoring tool with notifications
✅ [**Uptime Kuma**](https://github.com/louislam/uptime-kuma) - Self-hosted uptime monitoring tool with notifications
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@README.md` around lines 115 - 116, The Markdown link for the Uptime Kuma
entry is missing the closing “)” so the description is being included in the
URL; fix the line containing the link text "[**Uptime Kuma**]" by moving the
closing parenthesis to immediately after the URL
(https://github.com/louislam/uptime-kuma) and place the descriptive text "-
Self-hosted uptime monitoring tool with notifications" outside the link so it
reads: [**Uptime Kuma**](https://github.com/louislam/uptime-kuma) - Self-hosted
uptime monitoring tool with notifications.

✅ [**WAHA**](https://waha.devlike.pro/) - WhatsApp HTTP API (REST API) that you can configure in a click! 3 engines: WEBJS (browser based), NOWEB (websocket nodejs), GOWS (websocket go).

✅ [**Weaviate**](https://weaviate.io/) - An open-source AI-native vector database with a focus on scalability and ease of use. It can be used for RAG, hybrid search, and more.
Expand Down
15 changes: 15 additions & 0 deletions docker-compose.yml
Original file line number Diff line number Diff line change
Expand Up @@ -1276,3 +1276,18 @@ services:
timeout: 10s
retries: 5
start_period: 30s

uptime-kuma:
image: louislam/uptime-kuma:2
container_name: uptime-kuma
profiles: ["uptime-kuma"]
restart: unless-stopped
environment:
UPTIME_KUMA_WS_ORIGIN_CHECK: bypass
Comment on lines +1285 to +1286

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Inherit shared proxy env for outbound notifications.

Uptime Kuma performs outbound HTTP calls (webhooks/alerts), so it should inherit the shared proxy anchor like other outbound services.

Suggested fix
   environment:
+      <<: *proxy-env
       UPTIME_KUMA_WS_ORIGIN_CHECK: bypass

As per coding guidelines, services making outbound HTTP requests must use the shared proxy anchor <<: *proxy-env.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
environment:
UPTIME_KUMA_WS_ORIGIN_CHECK: bypass
environment:
<<: *proxy-env
UPTIME_KUMA_WS_ORIGIN_CHECK: bypass
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@docker-compose.yml` around lines 1285 - 1286, The Uptime Kuma service’s
environment block only sets UPTIME_KUMA_WS_ORIGIN_CHECK and does not inherit the
shared proxy variables; update the service's environment section to include the
YAML anchor inheritance by adding <<: *proxy-env alongside the existing
UPTIME_KUMA_WS_ORIGIN_CHECK so the container uses the shared proxy settings for
outbound HTTP calls (reference the environment block and the
UPTIME_KUMA_WS_ORIGIN_CHECK key and the *proxy-env anchor).

volumes:
- uptime_kuma_data:/app/database
Comment on lines +1287 to +1288

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

Declare uptime_kuma_data in top-level volumes.

This service references a named volume that isn’t declared, which can fail compose validation/start.

Suggested fix
 volumes:
   appsmith_data:
+  uptime_kuma_data:
   caddy-config:
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@docker-compose.yml` around lines 1287 - 1288, The compose file references the
named volume uptime_kuma_data under the service volumes section but does not
declare it at the top-level; add a top-level volumes entry named
uptime_kuma_data (e.g., under the top-level "volumes:" block) so docker-compose
validation/start succeeds and the service's volume mapping "-
uptime_kuma_data:/app/database" is resolved.

healthcheck:
test: ["CMD-SHELL", "wget -qO- http://localhost:3000/ || exit 1"]
interval: 30s
timeout: 10s
retries: 5
Comment on lines +1289 to +1293

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Align healthcheck with actual service port and bypass proxy vars.

Current healthcheck target (localhost:3000) is inconsistent with your Caddy upstream (:3001), and it doesn’t clear proxy vars as required by repo rules.

Suggested fix
   healthcheck:
-      test: ["CMD-SHELL", "wget -qO- http://localhost:3000/ || exit 1"]
+      test: ["CMD-SHELL", "http_proxy= https_proxy= HTTP_PROXY= HTTPS_PROXY= wget -qO- http://localhost:3001/ || exit 1"]
       interval: 30s
       timeout: 10s
       retries: 5

As per coding guidelines, healthchecks must bypass proxy by clearing http_proxy/https_proxy/HTTP_PROXY/HTTPS_PROXY.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
healthcheck:
test: ["CMD-SHELL", "wget -qO- http://localhost:3000/ || exit 1"]
interval: 30s
timeout: 10s
retries: 5
healthcheck:
test: ["CMD-SHELL", "http_proxy= https_proxy= HTTP_PROXY= HTTPS_PROXY= wget -qO- http://localhost:3001/ || exit 1"]
interval: 30s
timeout: 10s
retries: 5
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@docker-compose.yml` around lines 1289 - 1293, Update the healthcheck test to
hit the service port used by Caddy (:3001) and clear proxy environment variables
before invoking wget; replace the current test array in the healthcheck block
with a CMD-SHELL command that unsets
http_proxy/https_proxy/HTTP_PROXY/HTTPS_PROXY (e.g. via env -u ...) and then
runs wget -qO- http://localhost:3001/ || exit 1 so the probe bypasses any proxy
and targets the correct upstream.

1 change: 1 addition & 0 deletions scripts/04_wizard.sh
Original file line number Diff line number Diff line change
Expand Up @@ -67,6 +67,7 @@ base_services_data=(
"ragflow" "RAGFlow (Deep document understanding RAG engine)"
"searxng" "SearXNG (Private Metasearch Engine)"
"supabase" "Supabase (Backend as a Service)"
"uptimekuma" "Uptime Kuma (Uptime Monitoring)"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

Use the exact compose profile id in wizard (uptime-kuma).

uptimekuma won’t match profiles: ["uptime-kuma"], so the service selection won’t actually enable the container.

Suggested fix
-    "uptimekuma" "Uptime Kuma (Uptime Monitoring)"
+    "uptime-kuma" "Uptime Kuma (Uptime Monitoring)"
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
"uptimekuma" "Uptime Kuma (Uptime Monitoring)"
"uptime-kama" "Uptime Kuma (Uptime Monitoring)"
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@scripts/04_wizard.sh` at line 70, The wizard uses the wrong service
identifier string "uptimekuma" which doesn't match the compose profile id
"uptime-kuma"; update the mapping entry in scripts/04_wizard.sh so the left-hand
key equals the exact profile id "uptime-kuma" (i.e., replace "uptimekuma" with
"uptime-kuma") so that the service selection toggles the correct compose profile
in the profiles: ["uptime-kuma"] check.

"waha" "WAHA – WhatsApp HTTP API (NOWEB engine)"
"weaviate" "Weaviate (Vector Database with API Key Auth)"
)
Expand Down
3 changes: 3 additions & 0 deletions scripts/07_final_report.sh
Original file line number Diff line number Diff line change
Expand Up @@ -103,6 +103,9 @@ fi
if is_profile_active "postiz"; then
echo -e " ${GREEN}*${NC} ${WHITE}Postiz${NC}: Create your account on first login"
fi
if is_profile_active "uptime_kuma"; then
echo -e " ${GREEN}*${NC} ${WHITE}Uptime Kuma${NC}: Register your account on first login"
fi
Comment on lines +106 to +108

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Profile name mismatch prevents Uptime Kuma guidance from showing.

The check uses uptime_kuma, but the profile introduced in compose is uptime-kuma.

Suggested fix
-if is_profile_active "uptime_kuma"; then
+if is_profile_active "uptime-kuma"; then

As per coding guidelines, scripts should use is_profile_active "myservice" with the actual profile id.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@scripts/07_final_report.sh` around lines 106 - 108, The profile check uses
the wrong profile id: change the call to is_profile_active from "uptime_kuma" to
"uptime-kuma" so it matches the compose profile; update the string passed to
is_profile_active (the call near the Uptime Kuma echo block) to "uptime-kuma"
and keep the echo message as-is.

if is_profile_active "gost"; then
echo -e " ${GREEN}*${NC} ${WHITE}Gost Proxy${NC}: Routing AI traffic through external proxy"
fi
Expand Down
10 changes: 10 additions & 0 deletions scripts/generate_welcome_page.sh
Original file line number Diff line number Diff line change
Expand Up @@ -354,6 +354,16 @@ if is_profile_active "postiz"; then
}")
fi

# Uptime Kuma
if is_profile_active "uptime-kuma"; then
SERVICES_ARRAY+=(" \"uptime-kuma\": {
\"hostname\": \"$(json_escape "$UPTIMEKUMA_HOSTNAME")\",
\"credentials\": {
\"note\": \"Create account on first login\"
}
}")
fi
Comment on lines +357 to +365

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Use the correct env var for Uptime Kuma hostname.

UPTIMEKUMA_HOSTNAME doesn’t match the expected key pattern used elsewhere (UPTIME_KUMA_HOSTNAME), so the generated welcome URL will be blank/wrong.

Suggested fix
-      \"hostname\": \"$(json_escape "$UPTIMEKUMA_HOSTNAME")\",
+      \"hostname\": \"$(json_escape "$UPTIME_KUMA_HOSTNAME")\",
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@scripts/generate_welcome_page.sh` around lines 357 - 365, The Uptime Kuma
block in scripts/generate_welcome_page.sh uses the wrong environment variable
name UPTIMEKUMA_HOSTNAME; update the template to use the correct
UPTIME_KUMA_HOSTNAME so the generated SERVICES_ARRAY entry contains the real
hostname. Locate the block that appends to SERVICES_ARRAY for "uptime-kuma" and
replace references to UPTIMEKUMA_HOSTNAME with UPTIME_KUMA_HOSTNAME (preserve
the json_escape call and surrounding structure) so the welcome URL is populated
correctly.


# WAHA
if is_profile_active "waha"; then
SERVICES_ARRAY+=(" \"waha\": {
Expand Down
8 changes: 8 additions & 0 deletions welcome/app.js
Original file line number Diff line number Diff line change
Expand Up @@ -420,6 +420,14 @@
category: 'tools',
docsUrl: 'https://docs.python.org'
},
'uptime-kuma': {
name: 'Uptime Kuma',
description: 'Uptime Monitoring Dashboard',
icon: 'UK',
color: 'bg-[#5CDD8B]',
category: 'monitoring',
docsUrl: 'https://github.com/louislam/uptime-kuma'
}
'cloudflare-tunnel': {
Comment on lines +430 to 431

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Verify the exact missing-comma pattern between uptime-kuma and cloudflare-tunnel entries.
rg -nP -C2 "docsUrl:\s*'https://github.com/louislam/uptime-kuma'\s*\n\s*}\s*\n\s*'cloudflare-tunnel':\s*{" welcome/app.js

Repository: kossakovsky/n8n-install

Length of output: 49


🏁 Script executed:

# First, check if the file exists and find the SERVICE_METADATA object
fd -p welcome/app.js

Repository: kossakovsky/n8n-install

Length of output: 81


🏁 Script executed:

# Search for uptime-kuma entry to locate it precisely
rg -n "uptime-kuma" welcome/app.js -A 8 -B 2

Repository: kossakovsky/n8n-install

Length of output: 785


🏁 Script executed:

# Also check the cloudflare-tunnel entry context
rg -n "cloudflare-tunnel" welcome/app.js -A 3 -B 3

Repository: kossakovsky/n8n-install

Length of output: 351


Add a comma after the uptime-kuma entry to fix JavaScript syntax error.

Line 430 closes the uptime-kuma object, but line 431 immediately starts the next property without a comma separator. This breaks the SERVICE_METADATA object literal and prevents the script from parsing.

Proposed fix
         'uptime-kuma': {
             name: 'Uptime Kuma',
             description: 'Uptime Monitoring Dashboard',
             icon: 'UK',
             color: 'bg-[`#5CDD8B`]',
             category: 'monitoring',
             docsUrl: 'https://github.com/louislam/uptime-kuma'
-        }
+        },
         'cloudflare-tunnel': {
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
}
'cloudflare-tunnel': {
'uptime-kuma': {
name: 'Uptime Kuma',
description: 'Uptime Monitoring Dashboard',
icon: 'UK',
color: 'bg-[`#5CDD8B`]',
category: 'monitoring',
docsUrl: 'https://github.com/louislam/uptime-kuma'
},
'cloudflare-tunnel': {
🧰 Tools
🪛 Biome (2.4.6)

[error] 431-431: expected , but instead found 'cloudflare-tunnel'

(parse)

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@welcome/app.js` around lines 430 - 431, The SERVICE_METADATA object has a
missing comma after the 'uptime-kuma' entry which causes a JavaScript syntax
error; edit the SERVICE_METADATA definition to insert a trailing comma after the
closing brace for the 'uptime-kuma' object so the next property
'cloudflare-tunnel' is a valid sibling entry, then run a quick lint/parse to
confirm the object literal parses correctly.

name: 'Cloudflare Tunnel',
description: 'Zero-Trust Network Access',
Expand Down
Loading