Capture mesh-catalog at feat/r4g (2246ccc4) with the templates its manifests name and its predefined.json, and lay the copy out as a repository's root

The catalogue's manifests moved their content into template files and fall back to predefined keys, so a copy of module.json alone no longer passes the catalogue's own check; the bus's Dockerfile is gone from the catalogue.
2026-10-23 16:24:14 +02:00
parent 68c1220e87
commit 5ccc87f4d0
455 changed files with 12335 additions and 1333 deletions
@@ -0,0 +1,35 @@
+# Managed by the mesh (module systemd-networkd). Replaced on every push; edit
+# the catalogue instead.
+#
+# This machine's uplink is systemd-networkd's, and the mesh asks one thing of it
+# here (novox/hq ADR 0117): leave the private network's interface alone. mesh0
+# is the mesh's; the mesh brings it up and configures it itself. The mesh never
+# declares a link, an address, a route, a wireless network or its credentials,
+# nor a network file for any of this machine's own interfaces — those are
+# the operator's, and the link they make is the only channel the mesh reaches
+# this machine over.
+#
+# 00-: networkd applies the first .network file, in alphanumeric order across
+# every directory, that matches an interface, and ignores every later one even
+# if it matches too (systemd.network(5), [Match]). A catch-all of the operator's
+# — Name=*, Type=ether, a file with no [Match] at all — sorted before
+# this one would claim mesh0 first. 00 sorts before every numbered prefix the
+# man page recommends.
+#
+# Unmanaged=yes: "no attempts are made to bring up or configure matching links,
+# equivalent to when there are no matching network files" (systemd.network(5),
+# [Link], since 233). A match that ends the search, and does nothing else.
+#
+# No DNS setting, because none is needed: networkd never writes
+# /etc/resolv.conf. What it learns from a lease it hands only to
+# systemd-resolved, which the mesh does not run (novox/hq ADR 0196). So this
+# module declares the resolver file itself, beside this one, listing the
+# mesh's resolvers (novox/hq ADR 0223).
+#
+# The service is reloaded when this file changes, never restarted: a restart
+# drops the links networkd holds, this machine's channel to the mesh among them.
+[Match]
+Name=mesh0
+
+[Link]
+Unmanaged=yes
@@ -31,6 +31,11 @@
        "loads": [
          "uplink-tools"
        ]
+      },
+      {
+        "name": "files",
+        "kind": "archive",
+        "from": "files"
      }
    ]
  },
@@ -46,7 +51,7 @@
      "type": "file",
      "path": "/etc/systemd/network/00-mesh0.network",
      "mode": "0644",
-      "content": "# Managed by the mesh (module systemd-networkd). Replaced on every push; edit\n# the catalogue instead.\n#\n# This machine's uplink is systemd-networkd's, and the mesh asks one thing of it\n# here (novox/hq ADR 0117): leave the private network's interface alone. mesh0\n# is the mesh's; the mesh brings it up and configures it itself. The mesh never\n# declares a link, an address, a route, a wireless network or its credentials,\n# nor a network file for any of this machine's own interfaces — those are\n# the operator's, and the link they make is the only channel the mesh reaches\n# this machine over.\n#\n# 00-: networkd applies the first .network file, in alphanumeric order across\n# every directory, that matches an interface, and ignores every later one even\n# if it matches too (systemd.network(5), [Match]). A catch-all of the operator's\n# — Name=*, Type=ether, a file with no [Match] at all — sorted before\n# this one would claim mesh0 first. 00 sorts before every numbered prefix the\n# man page recommends.\n#\n# Unmanaged=yes: \"no attempts are made to bring up or configure matching links,\n# equivalent to when there are no matching network files\" (systemd.network(5),\n# [Link], since 233). A match that ends the search, and does nothing else.\n#\n# No DNS setting, because none is needed: networkd never writes\n# /etc/resolv.conf. What it learns from a lease it hands only to\n# systemd-resolved, which the mesh does not run (novox/hq ADR 0196). So this\n# module declares the resolver file itself, beside this one, listing the\n# mesh's resolvers (novox/hq ADR 0223).\n#\n# The service is reloaded when this file changes, never restarted: a restart\n# drops the links networkd holds, this machine's channel to the mesh among them.\n[Match]\nName=mesh0\n\n[Link]\nUnmanaged=yes\n"
+      "template": "files/00-mesh0.network"
    },
    {
      "id": "service",