How hexastack/hexabot works
Project type and purpose
• Full-stack, micro-modular AI chatbot/agent platform (“Hexabot v2”).
• Frontend admin panel (Next.js), backend REST/WebSocket API (NestJS + MongoDB), embeddable chat widget (React), plus Docker Compose orchestration and extension/plugin system.
File structure
• Top-level modules:
– /api: NestJS monolith subdivided into feature modules (chat, analytics, user, cms, nlp, migration, websocket, etc.).
– /frontend: Next.js admin UI with pages, components, contexts, hooks, and i18n assets.
– /widget: standalone React live chat widget.
– /docker: Docker Compose definitions for all services.
• Configuration files: Dockerfiles, .env examples, tslint/eslint, Nest CLI config.
• The API folder uses MVC (controllers, services, repositories, schemas) plus interceptors, guards, interceptors, plugin/extension subsystem.
README for additional insights
• Core features: LLM & NLU integration, multi-channel/widget, visual flow editor, plugin system, multi-lingual, analytics, real-time inbox/handover.
• Docker-driven local/dev/prod orchestration.
• CLI to scaffold and run services (ollama, redis, smtp, widget, nginx).
Detailed but not over-segmented
– At the top: Browser clients (Admin UI, Embedded Widget)
– Middle tier: Nginx → Docker network routing to Admin container & Widget container → API container
– Bottom tier: MongoDB, Redis, LLM Engine