How shoshan-anjo/novalytics-bot works
Project Type & Purpose
• Novalitics_Bot is a Python-based automation “bot” that monitors filesystem changes (via Config/selectors.json) and drives a browser to perform tasks.
• It uses an event-driven pattern: when a file event occurs, the bot reacts by executing browser automation steps.
File Structure
Top-level components:
├─ main.py (entry point / orchestrator)
├─ src/core (settings.py + logger.py)
├─ src/event/file_monitor.py (filesystem watcher)
├─ src/robot/browser_control.py (browser automation)
├─ src/utils (helpers.py, validators.py)
├─ Config (config.json, selectors.json)
├─ data (watched directory)
├─ logs (logging output)
└─ requirements.txt, setup.py, .env
Extract Architecture Insight from README
• Core modules handle configuration & logging.
• Event module implements monitoring logic.
• Robot module handles browser interactions.
• Utils provide shared functions & input validation.
Main Components
a. Orchestrator (main.py)
b. Core Service
– Configuration Loader (src/core/settings.py + Config/*.json)
– Logger (src/core/logger.py → logs/)
c. Event Monitor (src/event/file_monitor.py)
d. Robot Engine (src/robot/browser_control.py)
e. Utility Library (src/utils/helpers.py, validators.py)
f. Data Stores
– Input Data Folder (data/)
– Logs Store (logs/)
Relationships & Data Flow
1. Startup: Orchestrator reads environment (.env) and loads settings from Config/config.json.
2. Initialization:
– Logger is configured to write to logs/.
– FileMonitor is registered (Observer pattern) against data/ using selectors.json.
3. Runtime:
– FileMonitor detects create/modify events on data/*.
– On each event, FileMonitor emits an event to the Robot Engine.
– BrowserControl executes steps (using settings.selectors) to drive the browser.
– Helper & validator utilities enforce input correctness.
– All actions & errors are logged.
Architectural Patterns & Principles
• Observer / Event-Driven for file monitoring callbacks.
• Single Responsibility: each module (core, event, robot, utils) has a clear role.
• Layered structure: Orchestrator → Core → Event & Robot → Utils.
• Configuration-as-Code: JSON files separate from code.