From 3bbad88314b447112c50f387c22399894f09a378 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 21 Oct 2024 19:25:42 -0400 Subject: [PATCH] response --- ...ent_1_567cd57edce000c70a6bcc51605d5ae2._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/forum/Any_way_to_rename_or_delete_clusters__63__/comment_1_567cd57edce000c70a6bcc51605d5ae2._comment 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 index 0000000000..ef5105d1db --- /dev/null +++ b/doc/forum/Any_way_to_rename_or_delete_clusters__63__/comment_1_567cd57edce000c70a6bcc51605d5ae2._comment @@ -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. +"""]]