How bradykim7/pbot works
Project type and purpose
• This is a multi‐service Python project comprising two microservices:
• Hybabot: a Discord bot offering game info, music playback, recommendations, etc.
• Pricesota: a web crawler that scrapes product deals and notifies via Discord.
• Both run in Docker containers and share a MongoDB instance; they interact with external services (Discord API, FFmpeg).
File structure
• Top‐level folders:
• hybabot/ – Discord bot code (entry point newbot.py, cogs, shared utilities, models, repos)
• pricesota/ – Web crawler code under src/ (configs, infrastructure/crawler, library, product/domain, service layer, utils, main.py)
• Dockerfile & Dockerfile_webcrawler – build containers for each service
• docker-compose.yml – orchestrates both services plus MongoDB
• Patterns & layering:
• Hybabot uses a command‐module pattern (cogs) with shared common models and repositories.
• Pricesota uses a layered domain‐driven structure (configs → infrastructure → domain/models/repositories → service → utils).
README insights
• Required services: MongoDB, FFmpeg, Discord API
• Deployment: environment variables via .env, Docker Compose for containers
• Features that drive architecture: bot command handling, music streaming, crawling with multiple adapters, notification publishing
Main components
• Hybabot Service (Docker Container)
• Discord Command Handler (cogs)
• Shared Common Layer (models, repositories, utils)
• Hero & Food Domain Modules (models + repos)
• Public Assets (static text files)
• Config & Constants modules
• FFmpeg subsystem (external dependency)
• Pricesota Service (Docker Container)
• Crawler Layer (PpomppuCrawler, QuasarzoneCrawler, generic WebCrawler)
• Domain Layer (product models, keyword alerts)
• Repository Layer (KeywordAlertRepository, ProductRepository)
• Service Layer (ProductService)
• Notification Library (DiscordLibrary)
• NLP utilities
• Config & Utils
• Shared Database
• MongoDB (collections for alerts, products, heroes, food)
• External Services
• Discord API (bot commands & notifications)
• FFmpeg (audio processing)
Relationships and data flows
• Hybabot: Discord API ←→ Command Handler → Repository → MongoDB
• Hybabot: Music commands → FFmpeg → Audio stream
• Pricesota: Scheduler/trigger → Crawler modules → ProductService → Repository → MongoDB
• Pricesota: On new deals → DiscordLibrary → Discord API
• Both containers connect to the same MongoDB instance defined in docker-compose
Architectural patterns & design principles
• Microservices: two distinct services in separate containers
• Layered architecture within each service (presentation/commands, domain, persistence, utilities)
• Adapter pattern for crawlers and notification library
• Dependency injection via config modules and environment variables
Technologies, frameworks, libraries
• Python 3.8+
• Discord.py (Discord interactions)
• youtube-dl & FFmpeg (music playback)
• MongoDB (persistent storage)
• Docker & Docker Compose (containerization)
• Custom crawler adapters for web scraping
• Component labels (e.g., “Hybabot Cogs”, “ProductService”)
• Grouped layers (e.g., “Domain”, “Infrastructure”, “Utilities”)
• Environment boundary (Docker Compose network)