fix(infra): service registry is backup/fallback, not primary

Primary: Tailscale mesh + internal PostgreSQL/SQLite
Backup:  InfinityFree MySQL (this file)

Use cases for backup path:
  - Edge nodes that cant reach mesh (ESP32, Cloudflare Workers)
  - Mesh-down fallback (Tailscale outage)
  - Cross-mesh discovery (different tailnets)
  - Low-impact config distribution
This commit is contained in:
Brandon Schneider 2026-05-30 21:19:24 -05:00
parent ebcf0571ec
commit aff285be30

View file

@ -2,8 +2,15 @@
"""
External Service Registry MySQL-backed node discovery and credential store.
Uses InfinityFree MySQL as an always-available, mesh-independent registry.
Any node with internet can register itself and discover others.
Backup/fallback registry. Primary discovery uses Tailscale mesh + internal infra.
This MySQL backend is for:
- Edge nodes that can't reach the mesh (ESP32, Cloudflare Workers)
- Mesh-down fallback (Tailscale outage)
- Cross-mesh discovery (nodes on different tailnets)
- Low-impact config distribution
Primary path: Tailscale mesh + internal PostgreSQL/SQLite
Backup path: This MySQL registry (InfinityFree, always available)
Schema:
nodes registered devices with capabilities and tier