Revert "feat(workflows): update registry host to 192.168.100.49 across multiple CI/CD files"

This reverts commit 855e061244.

deploy/k3s/README.md

@@ -124,7 +124,7 @@ kubectl apply -f deploy/k3s/addons/kite.yaml
 访问：
 
 - Kite dashboard: `http://<node-ip>:30082`
-- NAS 示例：`http://192.168.100.49:30082`
+- NAS 示例：`http://192.168.100.19:30082`
 
 注意：Kite 官方清单绑定了 `cluster-admin` 权限，只建议在可信内网使用，不要直接暴露到公网。
 
@@ -150,11 +150,11 @@ kubectl -n kube-system patch svc traefik -p '{"spec":{"externalTrafficPolicy":"L
 
 临时用 frpc/frps 做 TCP 隧道时，用户源 IP 通常不会穿透到 k3s；这类链路需要 proxy protocol 或 HTTP 反代写入可信 `X-Forwarded-For`，否则日志只能记录隧道出口/NAS 本地转发地址。
 
-例如 NAS IP 是 `192.168.100.49`：
+例如 NAS IP 是 `192.168.100.19`：
 
-- tenant admin: `http://192.168.100.49:30080`
-- ops admin: `http://192.168.100.49:30081`
-- tenant api: `http://192.168.100.49:30083`
+- tenant admin: `http://192.168.100.19:30080`
+- ops admin: `http://192.168.100.19:30081`
+- tenant api: `http://192.168.100.19:30083`
 
 ### 4.2 用域名 Ingress + HTTPS
 

deploy/scripts/deploy-images-to-k3s.sh

@@ -24,7 +24,7 @@ REMOTE_DIR="${REMOTE_DIR:-/opt/geo-rankly/releases}"
 WAIT_TIMEOUT="${WAIT_TIMEOUT:-10m}"
 DELETE_REMOTE_TAR="${DELETE_REMOTE_TAR:-true}"
 PULL_FROM_REGISTRY="${PULL_FROM_REGISTRY:-false}"
-REGISTRY_HOST="${REGISTRY_HOST:-192.168.100.49:13000}"
+REGISTRY_HOST="${REGISTRY_HOST:-192.168.100.19:13000}"
 REGISTRY_HOST="${REGISTRY_HOST#http://}"
 REGISTRY_HOST="${REGISTRY_HOST#https://}"
 REGISTRY_HOST="${REGISTRY_HOST%/}"

deploy/scripts/gitea-registry-images.sh

@@ -5,7 +5,7 @@ set -euo pipefail
 REPO_ROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/../.." && pwd)"
 MODE="${1:-ensure}"
 
-REGISTRY_HOST="${REGISTRY_HOST:-192.168.100.49:13000}"
+REGISTRY_HOST="${REGISTRY_HOST:-192.168.100.19:13000}"
 REGISTRY_HOST="${REGISTRY_HOST#http://}"
 REGISTRY_HOST="${REGISTRY_HOST#https://}"
 REGISTRY_HOST="${REGISTRY_HOST%/}"