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

list proxied remotes and cluster gateways in git-annex info

Browse source 
Wanted to also list a cluster's nodes when showing info for the cluster,
but that's hard because it needs getting the name of the proxying
remote, which is some prefix of the cluster's name, but if the names
contain dashes there's no good way to know which prefix it is.
This commit is contained in:
Joey Hess 2024-06-30 11:14:13 -04:00
parent 28f5c47b5a
commit 3d646703ee
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 36 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

13
doc/tips/clusters.mdwn
View file

@ -12,16 +12,21 @@ To use a cluster, your repository needs to have its gateway configured as a
remote. Clusters can currently only be accessed via ssh. This gateway
remote is added the same as any other git remote:
git remote add bigserver me@bigserver:annex
$ git remote add bigserver me@bigserver:annex
The gateway publishes information about the cluster to the git-annex
branch. So you may need to fetch from it to learn about the cluster:
git fetch bigserver
$ git fetch bigserver
That will make available an additional remote for the cluster, eg
"bigserver-mycluster", as well as some remotes for each node eg
"bigserver-node1", "bigserver-node2", etc.
"bigserver-mycluster", as well as some remotes for each node.
$ git annex info bigserver
...
gateway to cluster: bigserver-mycluster
proxying: bigserver-node1 bigserver-node2 bigserver-node3
...
You can get files from the cluster without caring which node it comes
from: