sarkyboy commited on
Commit
7b5a948
·
1 Parent(s): 832d83b

chore: switch to MANAGEMENT_PASSWORD env var auth (bypass bcrypt issues)

Browse files
Files changed (2) hide show
  1. config.yaml +1 -1
  2. entrypoint.sh +3 -3
config.yaml CHANGED
@@ -4,7 +4,7 @@ port: 8317
4
  # Remote management settings
5
  remote-management:
6
  allow-remote: true
7
- secret-key: "$2a$10$fF0lzStmVciEn3Q/qzV2..EKJB3FUwWN8l3mf.JiZ.IgPMHfhARkG"
8
  disable-control-panel: false
9
 
10
  # Authentication directory
 
4
  # Remote management settings
5
  remote-management:
6
  allow-remote: true
7
+ # secret-key removed; using MANAGEMENT_PASSWORD env var instead
8
  disable-control-panel: false
9
 
10
  # Authentication directory
entrypoint.sh CHANGED
@@ -16,9 +16,9 @@ if [ -n "$API_KEYS" ]; then
16
  [ -n "$key" ] && echo " - \"$key\"" >> "$CONFIG"
17
  done
18
  fi
19
-
20
- # 管理面板密钥已在 config.yaml 中以 bcrypt 哈希形式硬编码
21
- # 登录密码: sarky880309 (对应哈希已预计算)
22
 
23
  # 注入代理 URL
24
  if [ -n "$PROXY_URL" ]; then
 
16
  [ -n "$key" ] && echo " - \"$key\"" >> "$CONFIG"
17
  done
18
  fi
19
+ # 使用 MANAGEMENT_PASSWORD 环境变量进行明文认证(绕过 bcrypt 哈希和配置文件写入问题)
20
+ export MANAGEMENT_PASSWORD="sarky880309"
21
+ echo "[entrypoint] MANAGEMENT_PASSWORD is set to hardcoded value"
22
 
23
  # 注入代理 URL
24
  if [ -n "$PROXY_URL" ]; then