How henicosa/conanbot works
Main Components
a) External Calendar Sources
• Multiple iCal calendar sources as external systems
b) Core Application Components
• Calendar Fetcher Service (conanbot.py)
• Calendar Processing Engine (icaltools.py)
• Calendar Merger (mrkalender.py)
• Logging System (applog.py)
• Web Interface (main.py, Flask application)
c) Storage/Configuration
• links.txt (calendar sources)
• Generated calendar data
• Application logs
Component Relationships
• External calendars → Calendar Fetcher
• Calendar Fetcher → Calendar Processing Engine
• Calendar Processing Engine → Calendar Merger
• Calendar Merger → Web Interface
• All components → Logging System
Technical Implementation Details
Elements:
• Docker container boundary (show containerization)
• Flask web server
• Static assets (CSS, HTML templates)
• Periodic scheduler (2-hour intervals)
Architectural Patterns to Highlight
• Microservice architecture (containerized application)
• Event-driven processing (periodic calendar updates)
• MVC pattern for web interface
• Pipeline pattern for calendar processing