How aswad546/sso-monitor works
Project type and purpose
• This is a full‑stack, microservices‑style web application (“SSO‑Monitor”) for continuously scanning millions of web sites’ login pages to detect and archive Single‑Sign‑On support.
• The “brain” directory is a Flask web front‑end + API; “worker” and “worker‑backend” are background compute services (crawler, analyzers, LLM classification); supporting services include MongoDB, MinIO, RabbitMQ, Prometheus, Promtail, searxng, Jupyter, and a cookie‑store microservice.
Top‑level directories as architectural clues
• brain/
– Flask app.py, blueprints for API and views, static assets, Jinja2 templates, config modules (MongoDB, RabbitMQ, MinIO, Celery, logging).
• worker/
– CLI‐driven Python service that pulls tasks, orchestrates login‐page detection (using worker/modules/*), writes results to MongoDB/MinIO via the API.
• worker‑backend/
– GPU‐accelerated classification backends (vllm serve for OS‑Atlas, Qwen2.5‑VL).
• watcher/
– lightweight Python service monitoring long‑running tasks/workers.
• cookie‑store/
– microservice for hosted cookie storage (Pipfile + script).
• searxng/, prometheus/, promtail/, rabbitmq/, jupyter/
– each an external service container for search aggregation, metrics collection, log shipping, message broker, notebook environment.
Key insights from README
• The system is launched via Docker‑Compose.
• Ports mapped: web UI (8080), DB UI (8081/9090), RabbitMQ (5672), MongoDB (27017), MinIO, Redis, Jupyter (8888), Prometheus (9090).
• Workflow: user triggers scan via web UI → brain pushes a Celery/RabbitMQ task → worker(s) fetch tasks, run analyzers, call external/searxng crawler, image classifiers (hosted externally via vllm serve), push results back → brain reads from MongoDB + MinIO and presents.