All checks were successful
CI/CD Pipeline / build-and-deploy (push) Successful in 12s
Lichess started rejecting anonymous requests to games/user and user/activity with a 404 (confirmed live: the same request with a valid bearer token got a normal 429 instead), which our code silently read as "user has no games" for every single tracked player, making periodic checks report zero activity across the board. Add LICHESS_APP_TOKEN and send it as a Bearer token on these two calls; it just needs to be any valid token; it does not need to belong to the tracked player. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
12 lines
541 B
Text
12 lines
541 B
Text
# Docker Compose Project Name
|
|
COMPOSE_PROJECT_NAME=lichess
|
|
|
|
# Telegram Bot Tokens (Test)
|
|
TELEGRAM_BOT_TOKEN=7903295042:AAGBO2k8pfBDy4RoLRFsknwE7z0N-thAPI8
|
|
ADMINPANEL_TELEGRAM_BOT_TOKEN=8588876086:AAHoZncfhTCbul1BblpvnZMzvz7jAYVFmcw
|
|
|
|
# Lichess personal API token used to authenticate outgoing requests to
|
|
# lichess.org (games/user, user/activity). Lichess started rejecting
|
|
# anonymous requests to these endpoints with a 404; any valid token works,
|
|
# it does not need to belong to a tracked player.
|
|
LICHESS_APP_TOKEN=lip_xxxxxxxxxxxxxxxxxxxx
|