git-annex-updatecluster(1)

✨ git-annex-updatecluster ✨

okay bestie, gather round, we're doing cluster bookkeeping today πŸ’– this one lives in the General Commands Manual and it's literally just git-annex updatecluster.


🌸 NAME 🌸

git-annex-updatecluster β€” update records of cluster nodes πŸ‘‘


πŸŽ€ SYNOPSIS πŸŽ€

git-annex updatecluster

that's it. that's the whole thing. no flags, no args, just vibes and a git-annex branch πŸ’…


πŸ¦‹ DESCRIPTION πŸ¦‹

so like, this command is the one that records the nodes of a cluster into the git-annex branch, and also sets up proxying to those nodes. the way that it works is so clean honestly. 🫢

run it in the repository that's gonna serve as the gateway to the cluster. that's its whole moment, that's its main character energy.

here's what it does under the hood, no cap:

  • it peeks at the git config remote.name.annex-cluster-node of every remote πŸ‘€
  • when that config is set to the name of a cluster that's already been initialized with git-annex initcluster, that node gets recorded in the git-annex branch ⭐

want to remove a node from a cluster? unset remote.name.annex-cluster-node and then run this command. bye bestie πŸ‘‹

want to add additional gateways to a cluster? run this command first, and after that, use git-annex-extendcluster. one thing at a time, we don't skip steps in this house 🧚


πŸ’œ OPTIONS πŸ’œ


🌈 SEE ALSO 🌈


πŸ‘‘ AUTHOR πŸ‘‘

Joey Hess <id@joeyh.name> β€” an absolute icon, fr fr πŸŽ€


okay that's the whole page, you ate it up, and if anyone asks: yes, this is from the General Commands Manual, it's git-annex-updatecluster(1), and it said what it said. go forth and cluster, bestie πŸŒΈπŸ’…πŸ¦‹