Telegram bot that monitors classified ads on willhaben.at and notifies you about new listings matching your keywords, plus price drops on tracked ads. Notifications include photos when available.

Prerequisites

Docker
Docker Compose (v2.x)

Quick Start

cp .env.example .env
# Edit .env with your bot token and database credentials
docker compose up -d --build

Deployment

Prerequisites

Docker 24+ (or any modern version with compose v2)
Docker Compose plugin installed (docker compose command works)
~500MB disk space for data volumes
Outbound HTTPS access to api.telegram.org and willhaben.at

Step-by-step Setup

Clone the repository and copy environment file:

git clone <repo-url> && cd willhaben-tracker
cp .env.example .env

Edit .env — at minimum set these values:

TELEGRAM_BOT_TOKEN — get from @BotFather on Telegram
POSTGRES_PASSWORD — any secure password

Start all services:

docker compose up -d --build

Verify health:

# All containers should show "Up" and the db container "healthy"
docker compose ps

# Worker logs should show "Bot started with long polling"
docker compose logs worker | grep "started"

Test the bot: send /start to your bot on Telegram, then /add <keyword> to create a search.

Updating the Stack

git pull && docker compose up -d --build

New database migrations are applied automatically when the Postgres container restarts with new migration files in supabase/migrations/.

Backing Up Data

# Full database dump
docker compose exec db pg_dump -U postgres postgres > backup_$(date +%F).sql

# Restore from backup
psql -h localhost -p 55632 -U postgres -d postgres < backup_2024-01-01.sql

Troubleshooting Common Issues

Problem	Solution
Postgres auth error on first boot	Volume may contain stale `pg_hba.conf`. Delete `data/db` and restart.
Studio shows "unhealthy" but APIs work	Cosmetic health check issue — ignore unless you can't browse tables.
Bot doesn't respond	Check `docker compose logs worker` for errors. Verify token in `.env`.

Configuration

Edit .env before first startup. All values are read by the worker and database services.

Variable	Description	Default
`TELEGRAM_BOT_TOKEN`	Token from @BotFather	(required)
`POSTGRES_USER`	PostgreSQL username	`postgres`
`POSTGRES_PASSWORD`	PostgreSQL password	(required)
`POSTGRES_DB`	Database name	`postgres`
`JWT_SECRET`	PostgREST JWT signing key	auto-generated default
`DEFAULT_INTERVAL_MINUTES`	Default scrape interval per search query	`60`
`ADMIN_TELEGRAM_IDS`	Comma-separated Telegram IDs with admin privileges	(none)

Architecture

Service	Image	Port	Purpose
db	postgres:15-alpine	55632	PostgreSQL database
rest	postgrest/postgrest:v12.2.0	—	REST API over the database
kong	kong:2.8.1	55621	Reverse proxy / gateway
studio	supabase/studio	55630	Supabase Studio admin UI
meta	supabase/postgres-meta:v0.84.2	—	Database metadata service
worker	(built from ./worker)	—	Scraper + Telegram bot

Telegram Commands

All users must be whitelisted before use. Run /start to activate your account.

Command	Access	Description
`/start`	Anyone	Activate account and show help message
`/add <keyword>`	Active user	Subscribe to keyword (shared across users)
`/list`	Active user	List your subscriptions with subscriber counts
`/delete <keyword_id>`	Active user	Unsubscribe from a keyword
`/stats`	Active user	Show queries count, ads tracked, notifications
`/adduser <id> [admin]`	Admin only	Add or promote a user by Telegram ID
`/removeuser <id>`	Admin only	Remove a user from the bot
`/users`	Admin only	List all registered users and their roles

Default Admin

On first boot, Telegram ID 298181113 is seeded as an admin user. Add additional admins via /adduser <telegram_id> admin.