How jamborjan/dorfinfobot works
Main Components Identification
a. News Scrapers (Node-RED based)
• Multiple scraper flows for different sources (Dierikon news, publications, Luzerner Zeitung, etc.)
• Implemented as Node-RED flows for flexibility
b. Central API (.NET Core)
• Core backend service
• Handles data persistence
• Provides REST endpoints
• Uses Entity Framework with SQLite
c. Channel Connectors (Node-RED based)
• Telegram connector
• Twitter connector
• Other potential channels
d. Web Interface (Blazor)
• Administrative interface
• News management
• Channel configuration
[News Sources]
• ↓
[Node-RED Scrapers] → [Central API (.NET Core)] → [Node-RED Connectors]
• ↓ ↑ ↓ ↓
[SQLite Database] ←––––––┘ [Web Interface] [Distribution Channels]
Detailed Component Representation
For the API layer, show:
• Controllers (News, Channel, Broadcast, Attachment)
• Entity Framework context
• Repository layer
• DTOs for data transfer
For Node-RED components, represent:
• Individual scraper flows
• Channel connectors
• Flow direction
• API integration points
Infrastructure Layer
Infrastructure components:
• Kubernetes cluster
• Traefik ingress
• Basic Auth middleware
• Exposed endpoints:
• file-dib.domain.com
• db-dib.domain.com
• api-dib.domain.com
• nr-dib.domain.com
Data Flow Representation
• News collection flow from sources through scrapers
• Data persistence flow to SQLite
• Broadcasting flow through channel connectors
• Administrative control flow through web interface