How henferper/mundobee works
Project type and purpose
• This is a full-stack IoT monitoring application for beehives.
• It ingests sensor data (temperature, humidity, bee movement) from ESP32 devices over MQTT, stores it in MariaDB, provides a REST+WebSocket API via a NestJS backend, and presents interactive dashboards in a Next.js+Tailwind CSS frontend. It also integrates Grafana (with Prometheus) for advanced metric visualization and Node-RED for data simulation.
File structure
• Top-level directories:
• /backend – NestJS monolith providing REST endpoints, WebSocket gateway, authentication, device/preset/metrics/configuration modules.
• /client – Next.js 13 “app router” based React frontend with Tailwind CSS, contexts, components, pages under (auth-routes) and (user-routes).
• /docker-compose.yml, /docker/ – container definitions for backend, client, nginx, plus mosquitto, node-red, grafana, prometheus, portainer.
• /mosquitto/, /node-red/, /grafana/, /prometheus/ – configuration and dashboards for external services.
README for additional insights
• Confirms all services: Frontend (Next.js), Backend (NestJS), Mosquitto (MQTT broker), MariaDB (relational DB), Grafana (visualization), Node-RED (simulation), Portainer.
• Mentions Prometheus for metrics, dashboards exposures at specific URLs.
a. Main components:
• ESP32 devices (sensors)
• Mosquitto MQTT Broker
• NestJS Backend (REST + WebSocket + MQTT subscriber + Prometheus metrics exporter)
• MariaDB Database
• Prometheus (scrapes /metrics from backend)
• Grafana (reads from Prometheus and optionally MariaDB)
• Next.js Frontend
• Node-RED (data simulator & test flows)
-