Internal ecosystem infrastructure ยท Flask ยท port 8448

The control console for the
LIGHT HOPE ecosystem

M448 scans, scores, and health-checks every project in the fleet, then gives operators one dashboard, REST API, and CLI to diagnose and heal what's broken.

Capabilities

Everything the fleet needs, in one place

Each capability below maps to real code in the repo โ€” scanners, analyzers, the Flask app, and the ops CLI.

๐Ÿ”Ž

Ecosystem scanning

Automated scanner walks every project, detecting tech stack, ports, databases, and auth systems on demand or on a schedule.

๐Ÿ“

8-dimension maturity scoring

Scores each project 0โ€“100 across infrastructure, auth, database, docs, testing, maintenance, deployment, and UI.

๐Ÿ”

Auth analysis & blueprint

Classifies each project's auth model (session, JWT, OAuth, Supabase, none) and produces a prioritized migration roadmap toward unified SSO.

๐Ÿ“ˆ

Health history tracking

Timestamped health records per project, queryable over the API, so you can see how a service trended over time.

๐Ÿ› ๏ธ

Ops CLI: diagnose & fix

Five commands โ€” stats, list-offline, diagnose, fix, check โ€” identify service-down / DNS / config issues and auto-repair the fixable ones.

๐ŸŒ

Dashboard + REST API

Interactive web dashboard with filtering, backed by a JSON API for projects, stats, auth roadmap, and ecosystem health.

โฐ

Background scheduler

Optional auto-scan runs on an interval so the ecosystem picture stays current without manual refreshes.

โ˜๏ธ

Cloudflare tunnel verification

Cross-checks configured DNS mappings against actual reachability, surfacing hosts that are routed but not responding.

๐Ÿงฌ

Gene-library stats

Aggregated views over reusable ecosystem components โ€” top genes, per-ecosystem breakdowns, and quality distribution.

Integrate

A REST API and a CLI, both real

Point your tooling at the JSON API, or drive daily operations straight from the terminal.

HTTP ยท localhost:8448
# Ecosystem-wide statistics
GET  /api/stats

# All projects, with filters
GET  /api/projects?min_score=70&limit=50

# Currently-running projects
GET  /api/projects/running

# Unified-auth migration roadmap
GET  /api/auth-roadmap

# Per-project health history
GET  /api/health-history/<project_id>

# Real-time ecosystem health + service liveness
GET  /api/ecosystem-health

# Trigger a fresh scan
GET  /api/refresh-scan

# Liveness probe
GET  /health
bash ยท scripts/ops_cli.py
# 1. See fleet status
python3 scripts/ops_cli.py stats

# 2. List offline projects
python3 scripts/ops_cli.py list-offline

# 3. Diagnose issues (all, or one project)
python3 scripts/ops_cli.py diagnose
python3 scripts/ops_cli.py diagnose m432

# 4. Auto-fix what's fixable (DNS routes, configs)
python3 scripts/ops_cli.py fix m432

# 5. Deep health check on one host
python3 scripts/ops_cli.py check m432

# One-liner: diagnose + fix + re-check
python3 scripts/ops_cli.py diagnose && \
  python3 scripts/ops_cli.py fix && \
  python3 scripts/ops_cli.py stats
bash ยท smoke test
# Start the dashboard
./start.sh                 # โ†’ http://localhost:8448

# Run a fresh project scan
python3 scripts/project_scanner.py

# Analyze authentication across the fleet
python3 scripts/auth_analyzer.py

# Quick app smoke test
python3 -c "from app import app; \
  print(app.test_client().get('/health').json)"
Workflows

Built for daily operations

The console is designed around the things fleet operators actually do.

01

Daily health sweep

Run stats โ†’ list-offline โ†’ diagnose โ†’ fix in under a minute to catch and repair overnight drift.

02

Single-project triage

When one host misbehaves, check <id> pinpoints service / DNS / config faults and fix <id> repairs them.

03

Onboarding a new project

Scan picks up the new service automatically, scores its maturity, and flags missing auth or database from day one.

04

Auth modernization planning

The auth roadmap ranks which projects to move onto unified SSO first, based on maturity and current auth model.

Get started in three commands

Clone the repo, install dependencies, and bring up the dashboard on port 8448.

bash
cd m448_server_console
pip install -r requirements.txt
./start.sh   # open http://localhost:8448
Back to top ↑
About this page. M448 Server Console is internal infrastructure for operating the LIGHT HOPE project fleet โ€” not a commercial product. This page documents what the tool genuinely does and how to run it. It intentionally shows no uptime percentages, latency SLAs, customer counts, or pricing: any live fleet numbers (project totals, online ratios, response times) come from on-demand scans and are shown only inside the running dashboard and API, where they reflect real data at query time.