System health
Backends and task runners. Your worker reports a heartbeat to Redis after each successful cycle.
Backends
Task runners
Telegram session
checking…Make sure the API ID and hash below are saved first.
This forgets the session string in the database. Telegram itself is not notified.
Channels & groups
Cached list of every channel and group your account is a member of. Direct messages are excluded by design. Toggle Archive to start saving messages and media for that chat. Toggle Pushover to open a dialog where you can paste the per-channel Pushover app token. The global recipient user key is set once in the Configuration card below.
Configuration
These settings live in the user_config table in Supabase, scoped to your account.
Changes apply on your worker's next poll cycle — no restart needed.
Tips
- Step 1: Save your Telegram API ID + hash below, then complete the login flow above.
- Step 2: Click Refresh from Telegram in the Channels card — it'll list every channel and group you're in.
- Step 3: Toggle Archive on the chats you want to save. Your worker picks them up on its next poll (within the configured interval).
- Optional Pushover: Set the global Pushover user key below (your account key from pushover.net). Then per-channel, toggle Pushover and paste the app token for that channel's Pushover application.
- Storage backend: Each channel defaults to Supabase. Switch to Local (/data) for channels with very large files (e.g. 500 MB ZIPs) — make sure the
/datavolume is mounted in docker-compose. - Watch the System health card up top to confirm your worker and the shared keepalive runner are alive and all backends are reachable.