| 2026-09-19 |
Update gitbucket VM inventory: runs navi instance pilar
...
gitbucket VM now runs navi instance pilar (deployed 2026-09-19 by rei) in addition to GitBucket.
|
Add hosts inventory item for VM gitbucket (GitBucket + navi pilar)
...
navi instance pilar (profile navi_code) deployed on VM gitbucket 2026-09-19 by rei. Host doc + hosts inventory item created.
|
Create host doc for VM gitbucket: GitBucket + navi instance pilar (deployed 2026-09-19)
...
New navi instance pilar deployed on VM gitbucket (192.168.1.156) on 2026-09-19; host doc created per inventory creation workflow (docs field must point to an existing doc).
|
Fix radio repo last-commit year typo (2026-02-23 -> 2025-02-23)
...
Fix typo introduced in previous commit: radio repo last-commit year was changed to 2026 by mistake; restoring 2025-02-23 from the 2026-05-10 API snapshot.
|
Add VM disk layout and free-space observation for gitbucket VM (2026-09-19)
...
Disk-space check requested by owner; discovered VM disk path, partition layout and free space via read-only loop mount on hypervisor. No guest agent and no direct SSH into the VM.
|
| 2026-09-18 |
Document BugTrail service deployment: host doc + inventory (host, domain, service)
...
BugTrail deployed 2026-09-18 on host bugtrail (192.168.1.177): docker compose stack (postgres+server+caddy) on port 80, public https://bugtrail.gnexus.space via internal nginx proxy with separate Let's Encrypt certificate (CN=bugtrail.gnexus.space, expires 2026-12-17). DNS record already existed. Verified end-to-end: healthz ok, panel HTTP/2 200, git.gnexus.space unaffected.
|
Add bugtrail.gnexus.space proxy mapping with dedicated LE cert; refresh internal-proxy-vps doc and nginx proxy inventory
...
Issued dedicated Let's Encrypt certificate for bugtrail.gnexus.space on the internal proxy VPS (192.168.1.226), added HTTPS :443 server block to the bugtrail nginx site (proxy to 192.168.1.177:80), verified healthz/panel/git.gnexus.space. Documented the new mapping plus previously undocumented enabled sites (creds, fuckjira, transcribe-demo, vmk-marginator).
|
| 2026-09-17 |
Document host mine (192.168.1.160) — navi instance Kael (ex-Miner)
...
Host mine (192.168.1.160, user ubuntu, Ubuntu 22.04.5, Xeon X5650 12C, 15 GiB RAM) documented from a read-only self-report by the Kael agent via swarm peer protocol. Navi instance Kael (ex-Miner, renamed 2026-09-17, instance_id 347a599e-a98f-410f-98c3-ea21dd90b7a4) on port 8099, repo /home/ubuntu/navi-1 (commit 1fb0f2a), Postgres 127.0.0.1:5432, docker bridge br-161f7117df03. Owner hypothesis about former addresses 192.168.1.249/.229 checked: no traces in docs, inventory, secrets, or the 2026-05-10 network scan.
|
Update bugtrail inventory: navi-1 tsukiko instance, ports 8099/5432
...
Inventory hosts/bugtrail updated after navi-1 (tsukiko) deployment: navi.service active, ports 8099 (navi-server) and 5432 (postgres) listening, purpose set to navi-agent-instance. Doc 10-systems/hosts/bugtrail.md already committed in 9814867.
|
Document navi-1 (tsukiko) deployment on bugtrail: repo path, service, ports, hive, instance id
...
Deployed navi-1 instance tsukiko on bugtrail (2026-09-17): repo, service, ports, hive announce verified via SSH.
|
Add new LAN VPS bugtrail (192.168.1.177): host doc + hosts inventory item
...
New LAN VPS bugtrail@192.168.1.177 onboarded: read-only SSH recon verified login + sudo (same password), Ubuntu 22.04.5 LTS KVM VM (2 vCPU, 3.8 GiB RAM, 31G LVM), docker+containerd running with no containers, listening ports 22/53/43225, secondary IP 192.168.1.198 on enp1s0 (purpose unknown). Credentials stored in gnexus-creds secret d654f5aa-412b-4fe0-87ad-89cc640375bb. Purpose not yet specified by owner.
|
| 2026-09-16 |
Document navi.service (Navi Proxy, port 8099) on ovpn_reserv
...
Verified via SSH on 2026-09-16: VM ovpn_reserv (192.168.1.226) runs navi.service (systemd, user ubuntu, WorkingDirectory /home/ubuntu/navi-1, ExecStart .venv/bin/navi-server) listening on 0.0.0.0:8099 with /health endpoint. Config at /home/ubuntu/navi-1/.env (OLLAMA_API_KEY, OLLAMA_HOST=https://ollama.com). No ollama_backends.json exists. SSH access as user ubuntu (root denied). No secrets stored.
|
Document VM tg_bots (192.168.1.254) navi melody instance and Ollama key rotation
...
New doc 10-systems/servers/tgbots-vm-navi-melody.md: VM tg_bots (192.168.1.254, hostname tgbots) runs mardisbot.service and navi.service (navi instance melody, port 8099, WorkingDirectory /home/ubuntu/navi-1). Ollama API key rotated 2026-09-16 in /home/ubuntu/navi-1/.env; ollama_backends.json not present on this instance; backup .env.bak-ollama-20260916 created; service restarted and verified active with /health HTTP 200.
|
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.
|
Add service-host (192.168.1.176) doc and inventory: navi zoe instance + GHard panel
...
Rotated Ollama API key on navi zoe instance (192.168.1.176): updated OLLAMA_API_KEY in /home/ubuntu/navi-1/.env, restarted navi.service (active). No ollama_backends.json exists on the host. Documented host and service in gnexus-book (no secret values stored).
|
| 2026-09-12 |
MardisBot: poll schedule moved to Wed+Fri 19:00 Kyiv, PYTHONUNBUFFERED added to unit, backups documented
...
Расписание голосовалок MardisBot изменено 2026-09-12: чт+сб 08:00 → ср+пт 19:00 (days=(3,5), POLL_HOUR=19). Добавлен PYTHONUNBUFFERED=1 в юнит. Бэкапы на VM.
|
Update VM mine: running at 192.168.1.160, hosts vanilla Minecraft server
|
| 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.
|
Refresh libvirt VM list; document fuckjira at 192.168.1.175
...
fuckjira VM (192.168.1.175) was missing from the VM doc, making .175 appear free. Verified live via virsh + ARP MAC matching on 2026-09-10.
|
Document /backup and ZIP-update in mardisbot remote ops
...
mardisbot.md remote ops section extended: /backup (download code as ZIP) and ZIP-upload update (auto-backup, auto-rollback, .env/venv untouched) now available via MardisOpsBot v2.
|
MardisOpsBot v2 deployed: /backup + ZIP-update, sudoers stop/start, unit ReadWritePaths; tests 18/18
...
v2 deployed to VM tg_bots: /backup + ZIP-update added, sudoers gained stop/start, unit gained ReadWritePaths for MardisBot dir; sandbox tests 18/18 passed. Verified live via SSH.
|
Document NoNewPrivileges fix in mardisops unit
...
mardisopsbot.md: documented removal of NoNewPrivileges=true (it blocked sudo inside the service, broke /status) and the enrolled admin user_id 78389352.
|
Cross-link MardisOpsBot from mardisbot doc
...
Cross-link in mardisbot.md to the new MardisOpsBot remote ops channel (doc 10-systems/bots/mardisopsbot.md).
|
Add mardisops service inventory entry
...
Inventory item services/mardisops (applied earlier via apply_pending_change) committed; doc 10-systems/bots/mardisopsbot.md was already committed in a2d5eb9.
|
Add MardisOpsBot (mardisops.service) on VM tg_bots
...
Deployed MardisOpsBot on VM tg_bots (192.168.1.254): mardisops.service active (running), enabled; files in /home/ubuntu/bots/MardisOpsBot; sudoers grant /etc/sudoers.d/99-mardisops-sudoers installed and validated. Documented in 10-systems/bots/mardisopsbot.md and services inventory.
|
MardisBot is ACTIVE on VM tg_bots (192.168.1.254); correct host and status
...
Live verification 2026-09-10: MardisBot is running on VM tg_bots (192.168.1.254), not on the tgbots VPS (192.168.1.178). Previous 'missing' status was wrong — the bot was redeployed to the VM after the VPS rebuild.
|