How kcnotes/gdmdashboard works
Main Components
a) Data Collection Layer:
• IRC Relay (external source)
• Report Handler (src/report_handler.ts)
• Wiki Population Service (src/populate_wikis.ts, src/populate_reports.ts)
b) Storage Layer:
• SQLite3 Database
• Fandom Wiki Pages (for storing processed data)
c) API Layer (src/api/):
• Dashboard API
• Discussions Interface
• DW Dimensions API
• Edit Interface
• Query Interface
d) Frontend Layer:
• Dashboard Interface (fandom_loaded/gdmdashboard.ts)
• Report Table Component (src/report_table.ts)
• Wiki Table Component (src/wiki_table.ts)
[IRC Relay] → [Report Handler] → [SQLite DB] → [Upload Service] → [Fandom Wiki Pages]
• ↑
[Wiki Population Services] -----------------------------------|
[External APIs] ←→ [API Interfaces] ←→ [Core Services]
[Dashboard Interface] ←→ [Report/Wiki Tables] ←→ [Fandom Wiki Pages]
Important Relationships to Highlight
• Data Flow:
• IRC Relay → Report Handler
• Population Services → Database
• Upload Service → Fandom Wiki Pages
• Dashboard Interface ←→ Wiki Pages
• API Dependencies:
• How api_interface.ts serves as a base interface
• Fake implementations for testing (src/fakes/)
Additional Elements
• A cron job scheduler symbol showing the daily upload_data.js execution
• Environment configuration dependencies (ACCESS_TOKEN)
• PM2 process management for long-running services
Technical Stack Indicators
• TypeScript as the primary language
• SQLite3 for data storage
• PM2 for process management
• Fandom's Wiki platform as the presentation layer
Deployment Context
A separate deployment view showing:
[PM2 Managed Processes]
• report_handler.js (continuous)
• populate_reports.js (one-time)
• upload_data.js (daily cron)