How shilin66/teams-bot works
Project type and purpose
• Key indicators: presence of bot.js/streambot.js, appManifest/manifest.json (Teams app manifest), Dockerfile, docker-compose.yml.
File structure
• Top-level files:
• index.js – likely the HTTP server entry point
• bot.js – the core Teams Bot logic
• streambot.js – a secondary bot or streaming endpoint
• models.js – data models or in-memory/session store
• Dockerfile/docker-compose.yml – container and orchestration configs
• appManifest/manifest.json – Teams app definition
• .env.example – configuration template
• No “frontend” folder: it’s purely a backend service exposing bot endpoints that Teams will call.
README
• Minimal content (“# dify-teams-bot”): confirms name but no deep architecture doc.
Detail without over-splitting
• Modules (index.js, bot.js, streambot.js, models.js)
• Environment injection (.env → Express/Bot)
• How appManifest/manifest.json is used in the deployment pipeline