Waukesha, Wisconsin · what’s new
What’s new.
Living log of what shipped. Launch is the deadline and the gates — charge the walk Friday, September 25, 2026. This page is the diary. Harborline is the demo plant, not a customer.
Wednesday, September 23, 2026
this ship
Play Store and App Store certification started
One Lantern for free and paid shops. The seat is the license — not a second paid app. Operator checklist is on /admin/store. Testers still sideload the APK or Add to Home Screen until Google and Apple list it.
- ●Package us.enlightenstudios.lantern on both stores. Apple Universal Links wait on the Team ID. Privacy page covers phone apps.
Thursday, September 17, 2026
this deploy
SQL-primary and honest Air/Stats are checked off
Doing cards durable-client-db, auth-sql-opt-in, and wifi-stats close honestly. Live Sign in already reads Postgres. Air and Stats count walk samples, not Tacoma fiction on a real building. Replica stays unused. First-building still waits on Michael’s street.
- ●durable-client-db — SQL-primary. JSON backup never deleted. LANTERN_DATABASE_REPLICA_URL parsed and unused.
- ●auth-sql-opt-in — LANTERN_SQL_READ=1 dual-read is the shipped opt-in. No second auth system.
- ●wifi-stats — walk-sample quality / band / SSID. Harborline labeled. Controller AP airtime not this phase. Not first-building.
Wednesday, September 16, 2026
this deploy
Collector overlay classifies clients; replica hook later
Imported closets classify phones, APs, printers, and PCs from the collector client name. Guest SSIDs are skipped. Remote replica is a documented env hook only — Sign in stays SQL-primary with JSON backup.
- ●Overlay matches switch FQDNs and names phones / APs / printers / cameras from the controller client. A neighbor phone on a PC stays a workstation.
- ●Meraki and UniFi skip guest / visitor SSIDs. Neighbor walk does not hop a guest SSID. No WAN sweep from Plesk.
- ●Aruba / Juniper / MikroTik map a pasted one-shape JSON; live pull stays a stub. Instant On never. Real switch pull is not done.
- ●LANTERN_DATABASE_REPLICA_URL is parsed and ignored for Sign in. Never delete lantern.json. Did not restyle frozen OG, rail, or plant lists.
this deploy
Store runs on Postgres — JSON is the backup
Sign in and getStore read local Postgres after a dual-read proof. mutateStore writes the full store (tickets, plants jsonb, boards) to SQL; lantern.json stays on disk as backup and is never deleted.
- ●LANTERN_SQL_READ=1 in the systemd drop-in. Password stays in /etc/lantern/database.env (0600, not git).
- ●Ten seats, operator scrypt hash unchanged. Empty or mismatched SQL falls back to JSON.
- ●Roll back by running deploy/postgres-sql-read.sh off — JSON remains source of truth.
this deploy
Postgres loaded — Sign in still JSON
Client data is copied into local Postgres. mutateStore dual-writes when LANTERN_DATABASE_URL is set. Live Sign in still reads lantern.json. JSON stays the backup until a dual-read is proven.
- ●Least-privilege role lantern, database lantern, password in /etc/lantern/database.env (0600, not git).
- ●Importer copies stored password hashes unchanged. Verify compares user counts and the operator hash without printing hashes.
- ●LANTERN_SQL_READ is unset. Do not point Sign in at an empty database.
this deploy
Store SQL map — still JSON Sign in
The opt-in Postgres schema now covers users, orgs, and the rest of the shop store (buildings, tickets, jobs, plants as jsonb, collector token hashes). Live Sign in still reads lantern.json. Production stays on JSON until LANTERN_DATABASE_URL is set and a dual-read is proven.
- ●Importer copies stored password hashes unchanged. Re-import does not overwrite a hash already in SQL.
- ●Generic DATABASE_URL is ignored so a stray env cannot cut Sign in over.
- ●Least-privilege grants live in deploy/postgres-grants.sql with no password. Disk is tight — no dumps in the web root, Postgres not installed on the Plesk box this pass.
this deploy
Launch board: durable store on top; JSON still live
Doing and Need to do now sort most important first. P1 is a durable client database (JSON→Postgres path already in the tree). Live Sign in still reads lantern.json. No production cutover. Frozen lists, rail, and OG are not workstreams.
- ●Doing: durable-client-db → auth-sql-opt-in → collector / plant-data-source → floors imported plant (function) → ten-day-beta. Samples and chrome sit below.
- ●Need to do: first-building first, then function work. Logo pick, print leave-behind, residential floors, samples, and styling sit lower. Hold chrome at the bottom.
- ●Remote replica is a later step on durable-client-db after dual-read is proven. Password hashes untouched. rsync still excludes data/.
this deploy
Opt-in Postgres schema for auth — Sign in still JSON
JSON on a root-only VM is not insecure because it is JSON. SQL is better later for concurrent writes and backups. Live Sign in still reads lantern.json. Hashes stay scrypt strings; Postgres does not encrypt them.
- ●LANTERN_DATABASE_URL unset = no-op. mutateStore still writes /root/Lantern/data/lantern.json.
- ●Schema covers orgs, users, password resets, and a reserved sessions table (cookies today).
- ●Importer copies stored password hashes unchanged. Fixture tests, not live hashes in git.
- ●Turn on later: install Postgres off the login path, apply deploy/postgres-auth.sql, dry-run the importer, then the systemd drop-in. Do not point Sign in at an empty database.
Tuesday, September 15, 2026
03:02 UTC
Live tenant file survives deploys
A release rsyncs the app and excludes data/. Operator sign-in is not reset by shipping code. The live store stays on the server data directory. This log does not discuss credential internals.
- ●113a6d9 03:02 UTC · Live — Keep operator credentials on the live data dir.
- ●Deploy never sends or overwrites the live tenant file.
- ●Production LANTERN_DATA_DIR is the server data directory, not the build tree.
Waukesha
The log stays current. The deadline stays on Launch.
Mike Cobus · Enlighten Studios. First day in this book is Tuesday, September 15, 2026. Every later ship adds a row here in the same commit.