harry/ForexBot2
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Docs: config.json deployment overlay (CLAUDE.md repo map, env table, test count)

Browse Source 
Documents the app_config.py / config.json overlay shipped in Tasks 1-4:
repo-map rows for app_config.py and config.json.example, env-var table
precedence (env -> config.json -> none, hardcoded fallbacks removed
2026-07-21), PlatformConfig/pair_signals overlay call order, and the
real 199-tests/13-modules suite count. Also fixes a stale SCAN_PAIRS
comment in telegram_bot.py that still named PlatformConfig.scan_pairs
as the deployment switch instead of config.json's scanning.pairs.

Claude-Session: https://claude.ai/code/session_01VPNF37MP9Kuv62B1VBrZ1b
This commit is contained in:
Harwinder Sekhon
2026-07-21 13:25:21 -04:00
parent 6e2fdbd684
commit b9633389fa
2 changed files with 21 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
telegram_bot.py
+5 -3
View File
@@ -113,9 +113,11 @@ _CHANNEL_ID_RAW = telegram_channel_id()
CHANNEL_ID: Optional[int] = int(_CHANNEL_ID_RAW) if _CHANNEL_ID_RAW else None
# ── Pairs & buttons ───────────────────────────────────────────────────
# The scanned pair list is config-driven: PlatformConfig.scan_pairs is
# the single switch for single- vs multi-pair operation. Buttons, WS
# subscriptions, and scan loops all derive from it.
# The scanned pair list is config-driven: `scanning.pairs` in config.json
# (read via app_config) is the single switch for single- vs multi-pair
# operation — `apply_pair_overrides` stamps it onto PlatformConfig.scan_pairs
# so the two stay in sync. Buttons, WS subscriptions, and scan loops all
# derive from it.
SCAN_PAIRS = list(_APP.scan_pairs)