From aff285be30feb896c381a4afe0e57d2a06fc8e29 Mon Sep 17 00:00:00 2001 From: Brandon Schneider Date: Sat, 30 May 2026 21:19:24 -0500 Subject: [PATCH] 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 --- 4-Infrastructure/shim/service_registry.py | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/4-Infrastructure/shim/service_registry.py b/4-Infrastructure/shim/service_registry.py index e4e2211c..0501f0a0 100644 --- a/4-Infrastructure/shim/service_registry.py +++ b/4-Infrastructure/shim/service_registry.py @@ -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