Ver Fonte

README: no cluster config in this (public) repo — it lives in the private cluster-config repo

Alexander Korolev há 1 semana atrás
pai
commit
f24e55b2eb
1 ficheiros alterados com 8 adições e 14 exclusões
  1. 8 14
      README.md

+ 8 - 14
README.md

@@ -1,4 +1,4 @@
-# sm121/recipes — recipe repo (data repo)
+# sm121/recipes — recipe repo (public data repo)
 
 The git recipe repo for the [sm121 launcher](https://git.kilork.org/sm121/launcher)
 DGX Spark / GB10 cluster toolkit. The launcher (and the Home Assistant
@@ -8,21 +8,17 @@ add-on) clone/pull this repo and serve from it:
   in the launcher repo)
 - **`docker-images/<dir>/`** — the image build contexts (source of truth;
   optional when the image is prebuilt in the registry)
-- **`config.toml`** — the shared cluster/config source of truth
-  (the add-on's base config)
 
 Design: [`specs/tech-architecture/ha-addon-recipe-repos.md`](https://git.kilork.org/sm121/launcher/blob/main/specs/tech-architecture/ha-addon-recipe-repos.md)
 in the launcher repo.
 
-## Credential-free contract
+## No cluster config here (on purpose)
 
-This repo may be **shared with other users** — nothing secret lives here.
-The add-on's effective config = this `config.toml` + the add-on options
-(the secrets): the SSH user/key, the HA URL/token, the registry base, and
-any `[mikrotik]` block (it carries a password) via the
-`sm121_config_extra` option. A cluster whose `extra_entities` name a
-mikrotik device (`SW2-MUC`) needs that block to resolve the entity —
-supplied per-install, never committed.
+This repo is **public** — and the cluster config (`[[clusters]]` with
+private node IPs, host keys, HA entity names) is not shareable. It lives
+in the **private** `sm121/cluster-config` repo, which the HA add-on
+fetches at boot (`sm121_base_config` option) and uses as its base config.
+The Mac launcher reads its own local config.
 
 ## Supersedes the old publish-bundle registry
 
@@ -37,6 +33,4 @@ install) still exist in the launcher but no longer commit to this repo.
 
 Recipes + build contexts move together (the served image must match the
 recipe revision): update this repo from the launcher repo's tracked state
-(`scripts/seed-recipe-repos.sh` in the launcher repo shows the layout;
-for this repo, copy `recipes/` + `docker-images/` and keep
-`config.toml` current, credential-free).
+(`scripts/seed-recipe-repos.sh` in the launcher repo shows the layout).