From ad6a796b3527b798dca8f43c6690fefa88fefefb Mon Sep 17 00:00:00 2001
From: you <you@example.com>
Date: Sat, 21 Mar 2026 23:00:01 +0000
Subject: [PATCH] Disable auto-seeding on empty DB - require --seed flag or
 SEED_DB=true

Previously db.seed() ran unconditionally on startup and would populate
a fresh database with fake test data. Now seeding only triggers when
explicitly requested via --seed CLI flag or SEED_DB=true env var.

The seed functionality remains available for developers:
  node server.js --seed
  SEED_DB=true node server.js
  node db.js  (direct run still seeds)
---
 package.json | 2 +-
 server.js    | 6 ++++--
 2 files changed, 5 insertions(+), 3 deletions(-)

diff --git a/package.json b/package.json
index 55959de0..dfb372bc 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "meshcore-analyzer",
-  "version": "2.1.0",
+  "version": "2.1.1",
   "description": "Community-run alternative to the closed-source `analyzer.letsmesh.net`. MQTT packet collection + open-source web analyzer for the Bay Area MeshCore mesh.",
   "main": "index.js",
   "scripts": {
diff --git a/server.js b/server.js
index 9b238704..6f5d2311 100644
--- a/server.js
+++ b/server.js
@@ -259,8 +259,10 @@ class TTLCache {
 const cache = new TTLCache();
 
 
-// Seed DB if empty
-db.seed();
+// Seed DB only when explicitly requested via --seed flag or SEED_DB=true env var
+if (process.argv.includes('--seed') || process.env.SEED_DB === 'true') {
+  db.seed();
+}
 
 const app = express();