skic-v1-playground/knowledge-wiki
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

wiki: sync 2026-08-02 18:08 UTC — 3 file(s) updated

Browse Source
This commit is contained in:
jarvis-at-skic
2026-08-02 18:08:31 +00:00
parent 9629e2dacc
commit 80e80ef2d8
3 changed files with 58 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
brain.md
+1
View File
@@ -54,6 +54,7 @@ _Last updated: 2026-08-01 05:37 UTC_
- TrueNAS SCALE 26.0.0-BETA.2 at lego-cloud.eu ✅
- Gitea: gitea.lego-cloud.eu (org: home-v1) ✅
- **General Gitea repository skill:** ✅ `gitea-repository-operations` — reusable API + SSH workflow for any repo; full wiki runbook at `wiki/infrastructure/gitea-repository-operations.md`
- **Gitea API credential (confirmed 2026-08-02):** use Bitwarden-provided `HL_V1_GITEA_ACCESS_TOKEN` for `gitea.lego-cloud.eu`; never use `GITHUB_TOKEN` for that instance or copy the Gitea token into `/opt/data/.env`. Bitwarden keys are exported without aliases and gateway restart is required after key changes.
- **world-v1/network-v1:** ✅ global Internet address book; IP-level mapping now separates registry holder, route origin, operator, and service. Initial records: `0.0.0.0` and `1.1.1.1`; wiki page at `wiki/infrastructure/network-v1.md`
- Keycloak: keycloak.lego-cloud.eu ✅
- Hermes Dashboard: jarvis-jr-v1.lego-cloud.eu ✅
channels/1526844602303123466.md
+21 -7
View File
@@ -1,22 +1,36 @@
# Channel Wiki: #jarvis-jr-v1-hermes-setup
_Channel ID: 1526844602303123466_
_Created: 2026-07-23 18:22 UTC_
_Last sync: 2026-07-23 18:22 UTC_
_Last sync: 2026-08-02 18:06 UTC_
## Purpose
<!-- What this channel is about -->
Hermes installation, persistent runtime configuration, secret management, and setup troubleshooting.
## Key Decisions
<!-- Important decisions made in this channel -->
- **CONFIRMED — Gitea credential (2026-08-02):** authenticated operations against `gitea.lego-cloud.eu` must use the Bitwarden Secrets Manager key/environment variable `HL_V1_GITEA_ACCESS_TOKEN`. Do **not** use `GITHUB_TOKEN` for this Gitea instance and do not copy the Gitea token into `/opt/data/.env`.
- **CONFIRMED — secret naming:** Hermes exports Bitwarden secret keys exactly as named; it does not create aliases. The briefly reported `HL_V1_GITEA_TOKEN` alias was stale cache information and was explicitly corrected.
- **CONFIRMED — restart semantics:** `/reset` only resets a conversation and does not reload process environment. A gateway restart is required after Bitwarden keys change so the gateway imports them.
## Active Topics
<!-- Currently active discussions/threads -->
- **Bitwarden setup:** enabled and operational. Live verification at sync time showed project access, `bws 2.0.0`, and one applied key: `HL_V1_GITEA_ACCESS_TOKEN` (value never exposed).
- **PENDING:** the gateway process observed during the 2026-08-02 conversation predated the corrected Bitwarden cache and had not imported `HL_V1_GITEA_ACCESS_TOKEN`; run `/restart` once, then verify the variable is present without printing its value.
## Key Context
<!-- Important context that persists across conversations -->
- `HERMES_HOME=/opt/data`; this is persistent storage, so Bitwarden configuration survives gateway/container restarts and container recreation as long as `/opt/data` remains mounted and `HERMES_HOME` is unchanged.
- Persistent Bitwarden components: token bootstrap in `/opt/data/.env`, configuration in `/opt/data/config.yaml`, managed CLI at `/opt/data/bin/bws`, and cache at `/opt/data/cache/bws_cache.json`.
- Bitwarden configuration uses `access_token_env: BWS_ACCESS_TOKEN`, a 300-second cache TTL, automatic `bws` installation, and exact-key export.
- A permissions incident made `/opt/data/.env` unreadable and caused repeated gateway `PermissionError` responses. It was fixed; at 2026-08-02 18:06 UTC both `/opt/data/.env` and `/opt/data/config.yaml` were owned by `hermes:hermes` with mode `0600`.
- `gitea-repository-operations`, `gitea-docusaurus-projects`, and the Discord knowledge-wiki Gitea creation workflow were updated to require `HL_V1_GITEA_ACCESS_TOKEN` and reject `GITHUB_TOKEN` for `gitea.lego-cloud.eu`. GitHub-specific workflows may continue using `GITHUB_TOKEN` for `github.com`.
- The blank human message `1533511724370624693` included `message.txt`; its CDN URL returned HTTP 403 when this sync attempted retrieval, so its contents remain **UNKNOWN**. Subsequent messages and live verification establish the setup outcome above.
## People & Roles
<!-- Key people who participate and their roles -->
- **RootAtSkic / Lego:** configured Bitwarden and directed the Gitea credential migration.
- **Hermes:** validates secret integration without revealing values and maintains Gitea-related skills.
## Action Items
<!-- Open action items from this channel -->
- [ ] **Owner: infrastructure operator / Lego — due date UNKNOWN:** restart the Hermes gateway once so `HL_V1_GITEA_ACCESS_TOKEN` is imported into the gateway environment.
- [ ] **Owner: Hermes — due date after restart:** verify gateway access to `HL_V1_GITEA_ACCESS_TOKEN` without displaying the value, then use it for future authenticated Gitea API operations.
## Source Anchors
- Latest processed human message: `1533516194106048725` (2026-08-02 16:45 UTC).
- Decision thread: human messages `1533507837391798413` through `1533516194106048725` (2026-08-02 16:12–16:45 UTC), with bot responses used only to establish implementation and verification outcomes.
meta/sync-log.md
+36
View File
@@ -1,5 +1,41 @@
# Sync Log
### Run #95 — 2026-08-02 18:06 UTC ✅
- **Channels scanned:** 26/26 (all accessible; up to the last 50 messages fetched from every current text channel; no channel-fetch failures).
- **New human activity since Run #94 (2026-08-02 14:02 UTC):** 16 messages in `#jarvis-jr-v1-hermes-setup` (16:12–16:45 UTC); no new human messages in the other 25 channels.
- **Durable knowledge captured:** Bitwarden Secrets Manager is operational with exact-key export; `gitea.lego-cloud.eu` operations must use `HL_V1_GITEA_ACCESS_TOKEN`, never `GITHUB_TOKEN`; Gitea skills were migrated; `/reset` does not reload secrets and one gateway restart remains pending. The `.env` permissions incident was fixed. The standing constraint remains unchanged: there is no ŽŪM AWS environment.
- **Artifact caveat:** attachment `message.txt` on message `1533511724370624693` returned HTTP 403 from Discord CDN during extraction; its contents are unknown, but subsequent messages and live checks established the resulting configuration/status.
- **Processed anchors (latest human message in each fetched window):**
- `#atea-storm` → `1532359647435165829` (2026-07-30 12:10 UTC)
- `#general` → `1532690074498760745` (2026-07-31 10:03 UTC)
- `#zeta-functions` → `1531221244530397214` (2026-07-27 08:46 UTC)
- `#network-v1` → `1529573612510511214` (2026-07-22 19:39 UTC)
- `#vssa-storm-1st-contract` → `1532462731142103040` (2026-07-30 18:59 UTC)
- `#dpvp-phase-2-opportunity` → `1532001823597264957` (2026-07-29 12:28 UTC)
- `#vssa-storm` → `1533032343021813930` (2026-08-01 08:43 UTC)
- `#vssa-dpvp-storm` → `1531567826039734333` (2026-07-28 07:43 UTC)
- `#vssa-dpvp-cvpa-audit` → `1533039197777297428` (2026-08-01 09:10 UTC)
- `#cogarch-model-v1-storm` → `1528684615898759258` (2026-07-20 08:46 UTC)
- `#cogarch-storm` → `1532481752365273090` (2026-07-30 20:15 UTC)
- `#cogarch-storm-skills` → `1529471826697392228` (2026-07-22 12:54 UTC)
- `#cogarch-storm-drawio-custom-shapes` → `1531292165874126998` (2026-07-27 13:28 UTC)
- `#cogarch-storm-cogarch-hub-web` → no human-message anchor (empty history)
- `#playground-eduard-melman` → `1531913577462497350` (2026-07-29 06:37 UTC)
- `#lego-as-enterprise-architect-within-vssa` → `1523377235153780836` (2026-07-05 17:17 UTC)
- `#jarvis-jr-test-001` → `1532723701039108117` (2026-07-31 12:16 UTC)
- `#jarvis-jr-enablement-voice` → `1519063294973841571` (2026-06-23 19:35 UTC)
- `#jarvis-jr-general` → `1521626344599851211` (2026-06-30 21:19 UTC)
- `#jarvis-jr-knowledge-wiki` → `1532722144897794130` (2026-07-31 12:10 UTC)
- `#jarvis-jr-truenas` → `1519380863719047178` (2026-06-24 16:37 UTC)
- `#lego-planner-v1` → `1532474154954260683` (2026-07-30 19:45 UTC)
- `#vssa-account-strategy` → `1524753167483408526` (2026-07-09 12:24 UTC)
- `#jarvis-jr-v1-hermes-setup` → `1533516194106048725` (2026-08-02 16:45 UTC) **NEW**
- `#jarvis-jr-v1-hermes` → `1531933519285063771` (2026-07-29 07:56 UTC)
- `#skic-v1-playground` → `1527409474833350687` (2026-07-16 20:19 UTC)
- **Files updated:** `channels/1526844602303123466.md`, `infrastructure/gitea-repository-operations.md`, `MEMORY.md`, and `sync-log.md`.
- **Inventory:** unchanged; the authoritative 26-channel list remains synchronized with `MONITORED_CHANNELS` and `discord/README.md`; all 26 channel wiki files are present.
- **Context refresh and Gitea push:** executed after these edits; real results reported in the delivered run summary.
### Run #94 — 2026-08-02 14:02 UTC ✅
- **Channels scanned:** 26/26 (all accessible; up to the last 50 messages fetched from every current text channel; no failures).
- **New human activity since Run #93 (2026-08-02 09:59 UTC):** None — all monitored channels were quiet.