How riozee/mikixbot works
Project type and purpose
• This is a multi-process Node.js chatbot aggregator (“Miki Bot”) that unifies Telegram, WhatsApp, RSS, statistics, and a command & database layer into separate child processes.
• Purpose: spawn and supervise all bot sub-processes, route messages via an IPC protocol, and persist data in MongoDB.
File structure
• main/main.js: the orchestrator (heart) – forks sub-processes, mediates IPC, restarts on error.
• main/subproses/: each JS is a self-contained child process:
• bot/telegram.js, bot/whatsapp.js – platform adapters (indera & anggota gerak)
• perintah.js – command handler (otak)
• database.js – MongoDB wrapper (memori)
• rss.js – RSS feed fetcher
• statistic.js – usage statistics collector
• main/alat/: utility modules for media & math conversions (gif_konversi.js, webp_konversi.js, mathjs.js).
• main/utils.js: IPC class (signals vs queries).
• res/: static JSON/text datasets (word lists, Quran surahs, translations).
• package.json: Node dependencies & scripts.
Inspect README for extra clues
• Outlines IPC model:
• “sinyal” (fire-and-forget) vs “kueri” (request/reply with id tracking)
• IPC.kirimSinyal / IPC.kirimKueri semantics
• Defines roles: heart/main.js, brain/perintah.js, memory/database.js, sensors/telegram & whatsapp.
• Lists external requirements: ffmpeg, imagemagick, webpmux, MongoDB Atlas.