make extendcluster also updatecluster
This avoids the user forgetting to do it and simplifies the documentation.
This commit is contained in:
parent
85f4527d74
commit
41a0817188
3 changed files with 10 additions and 4 deletions
|
@ -168,7 +168,6 @@ for NYC, and extending the cluster to there as well:
|
|||
AMS$ git remote add NYC me@nyc.example.com:annex
|
||||
AMS$ git-annex sync NYC
|
||||
NYC$ git-annex extendcluster NYC mycluster
|
||||
AMS$ git-annex updatecluster
|
||||
|
||||
A user can now add either AMS or NYC as a remote, and will have access
|
||||
to the entire cluster as either `AMS-mycluster` or `NYC-mycluster`.
|
||||
|
|
|
@ -17,8 +17,12 @@ 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 serves to the cluster,
|
||||
then run [[git-annex-updatecluster]] on each gateway.
|
||||
See the documentation of that command for details about configuring nodes.
|
||||
then run [[git-annex-updatecluster]]. See the documentation of that
|
||||
command for details about configuring nodes.
|
||||
|
||||
After running this command in the new gateway repository, it typically
|
||||
also needs to be run in the other gateway repositories as well,
|
||||
after adding the new gateway repository as a remote.
|
||||
|
||||
# OPTIONS
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue