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

improve

Browse source
This commit is contained in:
Joey Hess 2024-06-27 15:50:27 -04:00
parent 5b1971e2f8
commit 5ed690b690
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 4 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
doc/tips/clusters.mdwn
View file

@ -10,7 +10,7 @@ a node of the cluster.
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 remote:
remote is added the same as any other git remote:
git remote add bigserver me@bigserver:annex
@ -102,7 +102,7 @@ In the example above, the three cluster nodes were configured like this:
$ git config remote.node2.annex-cluster-node mycluster
$ git config remote.node3.annex-cluster-node mycluster
Finally, run `git-annex updatecluster` to record the cluster configuration
Finally, run [[git-annex-updatecluster]] to record the cluster configuration
in the git-annex branch. That tells other repositories about the cluster.
$ git-annex updatecluster
@ -148,7 +148,8 @@ accessed with ssh:
Setting up the cluster in NYC is different, rather than using
`git-annex initcluster` again (which would make a new, different
cluster), we ask git-annex to extend the cluster from AMS:
cluster), we ask git-annex to [[extend|git-annex-extendcluster]]
the cluster from AMS:
NYC$ git-annex extendcluster AMS mycluster