How eagletrt/backend-configuration works
Main Components Identification
• Nginx (Reverse Proxy/Load Balancer)
• MongoDB Database
• InfluxDB (implied by the influx-logger)
• Mosquitto (MQTT Broker)
• Ghost (Content Management System)
• Multiple Custom Services:
• Eagle App
• Influx Logger
• Telemetry Service
• Telemetry API
┌─ Client Layer
• External Clients/Applications
• Gateway Layer
• Nginx (Reverse Proxy with SSL/TLS)
• Application Services Layer
• Eagle App
• Telemetry API
• Telemetry Service
• Influx Logger
• Data Layer
• MongoDB
• InfluxDB
• Mosquitto (MQTT Broker)
Specific Elements
a) Gateway Layer:
• Nginx with SSL/TLS termination
• Logging paths (NGINX_LOGS_DIR)
• SSL certificate management (NGINX_LETSENCRYPT_DIR)
b) Application Services:
• Configuration file connections
• Environment variable dependencies
• Service interconnections
c) Data Layer:
• Database connections with authentication
• Persistent storage volumes
• Message broker topics/patterns
Additional Details
• Docker container boundaries
• Configuration file locations
• Environment variable dependencies
• Network connections
• Data flow directions
Relationships to Highlight
• How Nginx routes requests to different services
• How the Telemetry API interacts with databases
• How the Influx Logger processes and stores data
• Message flow through the MQTT broker