How robertmagic52/realmindreadingsystem works
This repository implements a screenshot and telemetry receiver with summary history and editable portal links. The main workflow accepts submissions through API routes, stores and serves them, and exposes a history page; separate routes manage summaries and portal configuration. The excerpts show server routing and persistence choices, but not the HTML contents or how pages call the API, so those relationships are not inferred.
Main entry points: index.js Express server · index.html Main page · history.html History page
Components 13
Web interface
- Main page
index.html - History page
history.html
Capture and history
- Express server
index.js - Health route
index.js - Submission routes
index.js - Submission storage
index.js - Summary routes
index.js - Summary storage
index.js - Deletion routes
index.js
Portal management
- Portal routes
index.js - Portal configuration
index.js
Other components
- Visitor
- MongoDB
Connections 17
- Visitor → Express server: sends requests
- Express server → Main page: serves at /
index.js - Express server → History page: serves at /history
index.js - Express server → Health route: registers route
index.js - Express server → Submission routes: registers routes
index.js - Express server → Summary routes: registers routes
index.js - Express server → Deletion routes: registers routes
index.js - Express server → Portal routes: registers routes
index.js - Submission routes → Submission storage: reads and writes
index.js - Submission routes → MongoDB: queries and saves
index.js - Summary routes → Summary storage: reads and writes
index.js - Summary routes → MongoDB: queries and saves
index.js - Deletion routes → Submission storage: deletes from
index.js - Deletion routes → Summary storage: deletes from
index.js - Deletion routes → MongoDB: deletes records
index.js - Portal routes → Portal configuration: reads and saves
index.js - Portal routes → MongoDB: queries and saves
index.js