dotfiles/vars/per-machine/phantom-ship/data-mesher-node-identity/peer.id/value at 6846faa5f138edd594e88201fa904af3eaa46e5e - dannydannydanny/dotfiles - Forgejo: Beyond coding. We Forge.

dannydannydanny/dotfiles

DannyDannyDanny 6846faa5f1 feat(clan): data-mesher + dm-pull-deploy wiring 🌊

Stage 4e-a of the clan migration. Set up signed-file gossip
(data-mesher, experimental, clan-core) and pull-based NixOS deploy
(dm-pull-deploy, experimental, clan-community) across both servers.

- sunken-ship is the data-mesher bootstrap node + dm-pull-deploy push
  role; phantom-ship joins via /dns/sunken-ship.clan/tcp/7946/... — the
  hostname resolves via /etc/hosts (clanHostsModule) to sunken-ship's
  ZT IPv6 since we don't run a DNS server for the clan domain.
- Both machines run the dm-pull-deploy default role with
  action="switch": they watch /var/lib/data-mesher/files/home/
  dm_pull_deploy/target and nixos-rebuild switch against the pushed
  git+…?rev=…&narHash=… flake ref on each change.
- Signing keys (shared + per-host status) generated via clan vars
  generate, ran on sunken-ship because data-mesher isn't packaged for
  aarch64-darwin.

The legacy dotfiles-rebuild timer stays installed as a fallback until
dm-pull-deploy is proven; a smart push timer on sunken-ship (calls
dm-send-deploy only when origin/main moves) comes next.

2026-04-20 11:38:01 +02:00

1 line

No EOL

52 B

Text

Raw Blame History

12D3KooWCZV7p7FiinyNJQTMhu9Us2AnzK6hbZiaw9bmWsaHUDoZ