How sharkesh-17/scoutops-student-service-portal works
ScoutOps lets campus users report and manage maintenance issues through a web UI and REST API, with issue records persisted in PostgreSQL. The sampled code shows the server starting the Express app, the app validating and handling issue requests, and its database calls. The README documents Prometheus/Grafana monitoring, but their runtime wiring was not sampled; those links reflect the documented architecture. The UI and monitoring branches are based on README capabilities and the available file tree.
Main entry points: server.js HTTP server · index.html Web interface · app.js Issue API · db.js Database access
Components 10
Issue access
- Web interface
public/index.html
Application runtime
- HTTP server
src/server.js - Issue API
src/app.js - Metrics endpoint
src/app.js
Issue storage
- Database access
src/db.js - PostgreSQL
Monitoring
- Prometheus
monitoring/prometheus.yml - Grafana
monitoring/grafana-datasource.yml - Alert rules
monitoring/alerts.yml
Other components
- Campus user
Connections 9
- Campus user → Web interface: uses
README.md - Web interface → HTTP server: sends requests
README.md - HTTP server → Issue API: starts app
src/server.js - Issue API → Database access: queries
src/app.js - Database access → PostgreSQL: reads and writes
README.md - HTTP server → Metrics endpoint: serves routes
src/server.js - Metrics endpoint → Prometheus: scrapes metrics
README.md - Prometheus → Grafana: feeds data
README.md - Grafana → Alert rules: supports alerts
README.md