hoelee
04bfd2d3a0
Same tick previously fired every due watch back-to-back (burst of N requests,
worst right after a restart when all watches are due at once). Now each watch
URL fetch is followed by a pause of FETCH_GAP_SECONDS (float, default 1, env
tunable; 0 disables) on both success and failure paths.
Also thread kw_fk_col into load_ignored_keywords() inside
send_pending_notifications() so the physical-FK lookup (445040a) actually takes
effect instead of silently falling back to the watch Link column.
16 lines
368 B
Bash
16 lines
368 B
Bash
# Copy to .env and fill in. All values are required.
|
|
|
|
# NocoDB (container DNS when on bridge_hoelee; LAN IP from a desktop):
|
|
NOCODB_URL=http://nocodb:10380
|
|
NOCODB_BASE_ID=poqw1zjw3hnsk37
|
|
NOCODB_TOKEN=
|
|
|
|
# Telegram alerts (@HoeleeAgentBot):
|
|
TELEGRAM_BOT_TOKEN=
|
|
TELEGRAM_CHAT_ID=5648309582
|
|
|
|
# Optional tuning:
|
|
TICK_SECONDS=60
|
|
FETCH_GAP_SECONDS=1
|
|
HEALTH_STALE_SECONDS=600
|