How anrijs/meshlog works
MeshLog Web ingests JSON reports from MeshCore logger firmware, stores decoded mesh activity and reporter observations in MySQL/MariaDB, and exposes it through a web interface and JSON API. The setup path initializes the database and admin account; the operational workflow is logger POST → decode/validate and persist records → browse or retrieve data. The README also documents reporter administration and configurable firmware reporting. Unsampled APIs and page internals are represented only where the README or source index supports their role; arrows reflect shown calls or documented interactions.
Main entry points: meshlog.class.php MeshLog service · meshlog.entity.class.php Entity persistence · setup.php Database and account setup · index.php Reporter admin API
Components 22
Ingestion
- Report endpoint
log.php - MeshLog service
lib/meshlog.class.php - Packet decoder
lib/meshlog.decoder.php
Mesh records
- Entity persistence
lib/meshlog.entity.class.php - MySQL database
- Mesh activity records
lib/meshlog.advertisement.class.php - Contacts
lib/meshlog.contact.class.php - Channels and messages
lib/meshlog.channel_message.class.php - Direct messages
lib/meshlog.direct_message.class.php - Reception reports
lib/meshlog.report.class.php - Reporter nodes
lib/meshlog.reporter.class.php - Telemetry
lib/meshlog.telemetry.class.php
Query interfaces
- Versioned JSON API
api/v1/all/index.php - API query routes
api/v1 - Activity web view
index.php
Administration
- Reporter administration
admin/index.php - Reporter admin API
admin/api/reporters/index.php - Session authorization
admin/api/loggedin.php - Database and account setup
setup.php - Schema migrations
lib/migration.class.php
Other components
- MeshCore logger
- Administrator
Connections 24
- MeshCore logger → Report endpoint: posts reports
README.md - Report endpoint → MeshLog service: calls insert
log.php - MeshLog service → Packet decoder: decodes packets
lib/meshlog.class.php - MeshLog service → Mesh activity records: creates records
lib/meshlog.class.php - MeshLog service → Reception reports: creates reports
lib/meshlog.class.php - MeshLog service → Entity persistence: uses persistence
lib/meshlog.class.php - Entity persistence → MySQL database: reads and writes
- Mesh activity records → Entity persistence: inherits persistence
lib/meshlog.advertisement.class.php - Contacts → Entity persistence: inherits persistence
- Channels and messages → Entity persistence: inherits persistence
- Direct messages → Entity persistence: inherits persistence
- Reception reports → Entity persistence: inherits persistence
lib/meshlog.report.class.php - Reporter nodes → Entity persistence: inherits persistence
- Telemetry → Entity persistence: inherits persistence
- Versioned JSON API → MeshLog service: queries data
api/v1/all/index.php - API query routes → MeshLog service: serves queries
api/v1/message_ids/index.php - Activity web view → MeshLog service: uses service
- Administrator → Reporter administration: manages reporters
README.md - Reporter administration → Reporter admin API: fetches reporter data
admin/index.php - Reporter admin API → Session authorization: checks session
admin/api/reporters/index.php - Reporter admin API → MeshLog service: uses service
- Database and account setup → Schema migrations: runs migrations
setup.php - Database and account setup → MeshLog service: checks database
setup.php - Database and account setup → MySQL database: initializes database
setup.php