| 2026-10-04 |
Deploy Gnexus Synapse: service doc, route update, host inventory update
...
Deployed 2026-10-04 by navi rei: docker compose stack (api+worker+postgres+redis) on gnsynapse 192.168.1.172:8013, public entry https://synapse.gnexus.space via nginx on internal-proxy-vps (.226) with fresh LE cert. Full pipeline smoke verified: event accepted 202, delivery delivered. Server-side call-home to gnexus-auth routed via LAN extra_hosts (override file). Secrets in gnexus-creds (gn-synapse-prod-secrets).
|
| 2026-10-03 |
Version 8a4814a: crypto migration done (salted KDF + AAD), alembic 0002, extension 0.2.4, new env vars (salt, CORS), update count ×7
...
Prod update 2026-10-03 10:21-10:30 UTC to 8a4814a: 5 commits with crypto changes (salted scrypt master KDF, AAD-bound ciphertexts, hardened endpoints). Required: new GNEXUS_CREDS_MASTER_KEY_SALT env var + explicit CORS origins (production validator), alembic 0002_notes_widen, crypto migration script (not in image — docker cp needed): 2 keys rewrapped, 130 ciphertexts rebound, idempotency verified. Extension 0.2.4 deployed. App crash-looped twice during setup (missing salt, missing CORS) — documented.
|
| 2026-10-02 |
Version 53acfb4 (Bearer fails closed); revocation semantics updated; extension rebuild recipe via node container; update count ×6
...
Prod update 2026-10-03 00:30 (21:29 UTC) to 53acfb4: Bearer auth fails closed (invalid/revoked token → 401, no session-cookie fallthrough) — resolves the 'revoked token still works' finding from 2026-10-02. Chrome extension rebuilt host-side in node:22 container (byte-identical to release, CRC-verified), stack rebuilt, DB untouched. Doc updated: revocation semantics corrected, extension rebuild recipe documented.
|
Add token revocation semantics: revocation immediate, extension popup cache TTL 5min can look alive, session-cookie fallthrough for same-browser requests
...
Owner reported a revoked token (657738c3459fe543, Chromium PC) still working. Verified: revocation is effective (revoked_at set, last_used_at frozen, audit shows access.failed bearer:gcr_657738c3 after revocation, empirical Bearer request → 401). Apparent 'still works' = extension popup cache (TTL 5 min) and/or session-cookie fallthrough in actor_from_request for same-browser requests. Documented semantics.
|
Version 287b7a0 (session death → sign-in without reload); update procedure count ×5
...
Prod update 2026-10-02 21:01 UTC to 287b7a0 (frontend-only: session death → sign-in without reload). No migrations, DB untouched, extension unchanged. Verified: app healthy, public health ok, front 200.
|
Version 27f95b4, extension 0.2.2 + pack v24; add Extension deployment section (zips committed in repo, no host rebuild); update procedure note about migrations
...
Prod update 2026-10-02 20:30 UTC to 27f95b4 (webhook fixes, revoked tokens UI, extension 0.2.2 + pack v24). DB untouched (no migrations). Verified: app healthy, public health ok, extension zips in container. Learned: extension zips are committed to repo and COPYed into image — no host-side rebuild needed (no node on host).
|
Add Backups section: daily pg_dump + .env snapshot, 10-day retention, root crontab 04:00 UTC; note extension secrets use source=domain and REST channel
...
Owner requested daily backups (10-day retention) after a false data-loss alarm. Backup script created, tested (EXIT=0, 64KB dump + .env snapshot), scheduled in root crontab at 04:00 UTC. Also documented: extension secrets use source=site domain and REST channel.
|
Add users section (2 accounts, all secrets owned by goldmikki), correct secret counts to 71 (69+2, 20/49 allow_mcp)
...
Live DB check 2026-10-02: secrets.user_id join shows all 71 secrets owned by goldmikki@gmail.com; second account lnikita2o1o@gmail.com (Popelous, SSO 2026-09-18) owns 0 secrets. Corrected counts: 69 actual + 2 archived, 20/49 allow_mcp split.
|
Add audit semantics section: snapshots persist after delete/rename, archived secrets stay in DB, audit IP is the internal proxy
...
Audit reconciliation 2026-10-02: audit keeps title snapshots after deletion/rename, archived secrets stay in DB, audit IP is the reverse proxy (192.168.1.226). Verified against live DB on gnexus-creds-host.
|
gnexus-creds: documented MCP/UI visibility semantics after false data-loss alarm
...
False "data loss" alarm investigated 2026-10-02: MCP search filters allow_mcp=true only and defaults to limit 20; UI paginates 20/page. DB intact (70 secrets). Documented to prevent recurrence.
|
gnexus-creds updated to 543d6ae (2026-10-02): splash on sign-in, extension 0.2.1
...
Service updated to 543d6ae on 2026-10-02 by rei (splash on sign-in, logout without SSO auto-login, extension 0.2.1); update procedure verified fourth time.
|
gnexus-creds updated to 3b5a00d (2026-10-02): extension 0.2.0 builds on download page
...
Service updated to 3b5a00d on 2026-10-02 by rei (extension 0.2.0 builds on download page); update procedure verified third time.
|
gnexus-creds updated to 02a2441 (2026-10-02): localization, mobile UX, extension design pack
...
Service updated to 02a2441 on 2026-10-02 by rei (localization en/uk/ru, mobile UX, extension design pack); update procedure re-verified.
|
| 2026-10-01 |
gnexus-creds updated to 4c6a4f7 (2026-10-01): documented local compose adaptation, update procedure, SSH access
...
Service updated to 4c6a4f7 on 2026-10-01 by rei; documented local compose adaptation, update procedure, and SSH access method.
|
| 2026-09-16 |
Add 2026-09-16 Ollama key rotation maintenance note to navi-zoe doc
...
Record the 2026-09-16 Ollama API key rotation on the zoe instance and the verified fact that no ollama_backends.json is used.
|
| 2026-09-11 |
Мониторинг NFS-шар: 4 шары online, руководство по добавлению
...
Добавлен раздел про мониторинг сетевых шар: текущие 4 шары, пошаговое руководство как добавить новую (mount → compose bind-mount :slave → POST /api/v1/shares → проверка), грабли с docker-compose down/up.
|
| 2026-09-10 |
Document navi zoe deployment on VM service (192.168.1.176)
...
navi zoe deployed on VM service (192.168.1.176) via deploy branch install.sh; joined hive swarm; mcp pinned to 1.27.1; embeddings on local Ollama 192.168.1.168.
|
Fleet hard-monitor: 18/18 серверов online, метод деплоя и грабли
...
Массовый деплой агентов завершён: 18/18 online. Задокументирован fleet-список, неохваченные хосты, метод деплоя и практические грабли (apt 404, py3.6 на gitbucket, диск 100%).
|
Отключён GHARD_ADMIN_TOKEN (UI не работает с токеном), исправлен compose-дефолт, добавлены MCP и заметки
...
UI не показывал сервер из-за GHARD_ADMIN_TOKEN (UI не подписывает запросы токеном) и дефолта change-me в compose. Токен отключён, compose исправлен.
|
Document hard-panel service on 192.168.1.176
...
Deployed GHard Monitor panel (docker) and hard-monitor agent on VM service (192.168.1.176). Secrets in gnexus-creds.
|
| 2026-09-04 |
Document gnexus-auth service; add gnbook VM and gnauth LAN IP to inventory; record shome user on smart-home-server
...
Applied pending changes: 20260904232033-1ff6d9a5 (gnexus-auth service doc), 20260904234541-85929c82 (create gnbook VM item), 20260904234543-e0b90cbe (gnauth LAN IP). VM-to-IP mapping verified via hypervisor ARP + virsh dumpxml MAC correlation on 192.168.1.130. SSH credentials for gnbook/gnauth stored in gnexus-creds (secret gnauth-gnbook-ssh). hosts.yml user:shome addition from earlier verified test session.
|
| 2026-05-21 |
Deploy gnexus-creds on 192.168.1.173:80 and document service
|