response
authorJoey Hess <joeyh@joeyh.name>
Mon, 21 Oct 2024 23:25:42 +0000 (19:25 -0400)
committerJoey Hess <joeyh@joeyh.name>
Mon, 21 Oct 2024 23:25:42 +0000 (19:25 -0400)
doc/forum/Any_way_to_rename_or_delete_clusters__63__/comment_1_567cd57edce000c70a6bcc51605d5ae2._comment [new file with mode: 0644]

diff --git a/doc/forum/Any_way_to_rename_or_delete_clusters__63__/comment_1_567cd57edce000c70a6bcc51605d5ae2._comment b/doc/forum/Any_way_to_rename_or_delete_clusters__63__/comment_1_567cd57edce000c70a6bcc51605d5ae2._comment
new file mode 100644 (file)
index 0000000..ef5105d
--- /dev/null
@@ -0,0 +1,14 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2024-10-21T23:11:11Z"
+ content="""
+The name of the cluster ends up in git-annex:proxy.log. So probably the
+easiest thing to do is to `git-annex initcluster` a new cluster with the new name,
+change the git configs remote.foo.annex-cluster-node to be set to the new
+name, and run `git-annex updatecluster`. 
+
+That will remove all the nodes from the old cluster name and add them to the new
+cluster name, and without any nodes left the old cluster name will never be
+displayed anywhere.
+"""]]