mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

updatecluster: support multiple gateways

Browse source 
Just look at the existing proxied remotes that correspond to already
existing nodes of the cluster, and keep those nodes in the cluster.
While adding any remotes of the local repo that are configured as
cluster nodes. This allows removing cluster nodes from the local repo
and updating, without it also removing nodes provided by other gateways.
This commit is contained in:
Joey Hess 2024-06-26 10:51:14 -04:00
parent 0b72b85df5
commit 02bf3ddc3f
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
3 changed files with 19 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

2
doc/git-annex-extendcluster.mdwn
View file

@ -16,7 +16,7 @@ gateway to the cluster. The `gateway` parameter is the name of that remote.
The `clustername` parameter is the name of the cluster.
The next step after running this command is to configure
any additional cluster nodes that this gateway provide to the cluster,
any additional cluster nodes that this gateway serves to the cluster,
then run [[git-annex-updatecluster]]. See the documentation of
that command for details about configuring nodes.

2
doc/git-annex-updatecluster.mdwn
View file

@ -9,7 +9,7 @@ git-annex updatecluster
# DESCRIPTION
This command is used to record the nodes of a cluster in the git-annex
branch. It should be run in each repository that will serve as a gateway
branch. It should be run in the repository that will serve as a gateway
to the cluster.
It looks at the git config `remote.name.annex-cluster-node` of