Main health signal. Used by Docker health checks.
Runtime overview including queue, cache, memory and resilience information.
Detailed resilience metrics when available.
Operational support endpoints for cache, circuit breaker and Telegram resilience inspection.
Start:
docker compose up -d --buildStop:
docker compose downFull reset including Redis and SQLite volume data:
docker compose down -vLogs:
docker compose logs -f rss-skull-bot
docker compose logs -f redis- Docker stores SQLite at
/app/data/production.db - local development typically uses
file:./dev.db - Prisma migrations are applied on container startup through
docker-entrypoint.sh
BullMQ workers require Redis. If Redis is unhealthy, feed checks and message delivery will degrade immediately.
Useful checks:
docker compose ps
docker compose logs redis --tail=100The repository includes a Node backup helper:
node scripts/backup-database.js backupRestore:
node scripts/backup-database.js restore <backup-file>Usually caused by another process using the same bot token.
Queue workers cannot schedule or process feed jobs.
If Prisma migration deployment fails, inspect container logs first. The current entrypoint tolerates migration failure so the app can still expose diagnostics.
Use the bot /status command and inspect /stats to verify recurring jobs and feed state.