How lincolnkermit/eyefinder works
EyeFinder is a browser-based CCTV discovery and monitoring map. Visitors explore camera locations, inspect stream status, and open feeds; operators manage camera records and access settings, review traffic metrics, and run health checks. The backend routes these requests to separate camera, administration, authentication, metrics, and scheduled-check handlers. Camera records use Supabase/PostgreSQL when configured, with local-file and seed-data fallbacks. The README documents the map, live status, feed redirection, and scheduled verification; unsampled frontend/API wiring is shown only where documented or marked unverified.
Main entry points: admin.js Admin API · db.js Camera store · server.js HTTP server · cameras.js Camera API
Components 21
Map and Admin UI
- Camera map
public/app.js - Admin portal
public/admin.js
HTTP API
- HTTP server
server.js - Camera API
api/cameras.js - Admin API
api/admin.js - Access API
api/auth.js - Health cron API
api/cron.js - Metrics API
api/metrics.js
Camera and Security Services
- Camera records
lib/seed.js - Stream health checks
lib/scraper.js - Access and validation
lib/security.js
Persistence and Telemetry
- Camera store
lib/db.js - Site settings
data/settings.json - Traffic telemetry
lib/metrics.js
Other components
- Map visitor
- Site operator
- Supabase / PostgreSQL
- Local camera files
data/cameras.json - Public camera streams
- Nominatim geocoder
- Vercel scheduler
Connections 31
- Map visitor → Camera map: opens map
README.md - Camera map → Camera API: loads cameras
- Camera map → Public camera streams: opens feed
README.md - Site operator → Admin portal: manages cameras
README.md - Admin portal → Admin API: admin actions
- HTTP server → Camera API: routes requests
server.js - HTTP server → Health cron API: routes requests
server.js - HTTP server → Admin API: routes requests
server.js - HTTP server → Metrics API: routes requests
server.js - HTTP server → Access API: routes requests
server.js - Camera API → Camera store: reads and writes
api/cameras.js - Camera API → Access and validation: checks access
api/cameras.js - Camera API → Camera records: loads seed
api/cameras.js - Admin API → Camera store: manages records
api/admin.js - Admin API → Access and validation: checks access
api/admin.js - Admin API → Stream health checks: uses probe
api/admin.js - Admin API → Camera records: loads seed
api/admin.js - Admin API → Nominatim geocoder: geocodes addresses
api/admin.js - Access API → Access and validation: verifies passkey
api/auth.js - Access API → Site settings: reads settings
- Health cron API → Camera store: loads and saves
api/cron.js - Health cron API → Stream health checks: checks streams
api/cron.js - Health cron API → Camera records: loads fallback
api/cron.js - Vercel scheduler → Health cron API: invokes scheduled check
README.md - Stream health checks → Access and validation: validates URLs
lib/scraper.js - Stream health checks → Public camera streams: probes streams
lib/scraper.js - Camera store → Camera records: falls back to seed
lib/db.js - Camera store → Supabase / PostgreSQL: reads and writes
lib/db.js - Camera store → Local camera files: falls back locally
lib/db.js - Metrics API → Traffic telemetry: records and summarizes
api/metrics.js - Metrics API → Access and validation: checks admin access
api/metrics.js