5 Commits

Include renames

Author	SHA1	Message	Date
jochen	fe2040c65e	Keep every password, token and API key the vault's, never a setting (hq issue 342) ... A setting outranked the vault: baserow, grafana, letta and unifi merged a layer's password over the ${secret:...} in their runtime config, and the gitea, home-assistant, icecast, influxdb, mailu and nextcloud clients read the settings file before the vault's file. A secret in a setting cannot be rotated and is read back by the settings verb. The four files now keep their password protected, so the controller refuses a setting of it. The six clients ignore a secret in the settings file and say so once, by key and never with the value; icecast reads its admin password from the vault's file. checks/secrets refuses a mergeable file whose secret a layer could replace; searxng's nested server.secret_key is listed as known until the controller protects a nested key.	2026-10-13 07:32:19 +02:00
jschoubben	5f74c41a3e	nextcloud: give the admin password a real _FILE variant, not an env-file ... The mesh's own check caught it: an env-file-loaded secret still reaches the process environment, readable via docker inspect and /proc (hq 04-ISSUES/041) -- the same class of exposure the file-based delivery exists to avoid. Added MESH_NEXTCLOUD_ADMIN_PASSWORD_FILE support to the client, matching the pattern the minio client already uses, and mounted the sealed admin secret directly rather than writing it into an env-file.	2026-09-25 13:42:21 +02:00
jschoubben	6e8c18afff	Resync hq ADR references 0044-0054 -> 0039-0049 after the hq record reconciliation	2026-09-05 12:49:16 +02:00
jschoubben	9e156a5b9e	Roll out the tool runtime to the remaining tools+events modules (ADR 0052/0051) ... Nineteen modules gain a broker-bound runtime container that serves the module's tools under its own scoped account: bazarr, gitea, grafana, home-assistant, icecast, influxdb, jackett, keycloak, mailu, nextcloud, nodered, nzbget, ombi, photos, portainer, qbittorrent, searxng, tautulli, verdaccio. Config is the assignment's, not the manifest's (ADR 0051): each client's fromEnv overlays a settings-merged config file (MESH_<M>_CONFIG_FILE) over its env fallbacks, so URL and credentials come from `settings set`, with the URL defaulting to the server on the node. nextcloud and mailu also mount the docker socket for their exec-based tools. Proven in the mesh-lab: assigned-grafana green — settings deliver the URL and token, the runtime reads the merged config and serves grafana's tools under the scoped account, with nothing in the manifest. Two gaps this surfaced are filed as hq issues 008 (a provider runtime's seal key) and 009 (a settings change does not restart a container runtime). Claude-Session: https://claude.ai/code/session_01LrgweAeERJYBg88c5cKDzF	2026-09-04 23:08:40 +02:00
jschoubben	eccfc70991	grafana, tautulli, nextcloud, nodered: full nox modules (ADR 0044/0046) ... grafana: status/datasources/dashboards/alerts tools, emits alert.firing. tautulli: activity/history/stats tools, emits watch.recorded. nextcloud: users/shares/apps/occ tools (occ via docker exec, shares over OCS), emits user.created/share.created. nodered: flows/nodes/deploy tools, emits flows.deployed inline from the deploy tool. All typecheck; manifests parse.	2026-09-04 02:43:20 +02:00