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

make extendcluster also updatecluster

Browse source 
This avoids the user forgetting to do it and simplifies the
documentation.
This commit is contained in:
Joey Hess 2024-06-27 15:34:45 -04:00
parent 85f4527d74
commit 41a0817188
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
3 changed files with 10 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

5
Command/ExtendCluster.hs
View file

@ -15,6 +15,7 @@ import Types.Cluster
import Config import Config
import Types.GitConfig import Types.GitConfig
import qualified Remote import qualified Remote
import qualified Command.UpdateCluster
import qualified Data.Map as M import qualified Data.Map as M
@ -27,7 +28,9 @@ seek (remotename:clustername:[]) = Remote.byName (Just clusterremotename) >>= \c
Just clusterremote -> Remote.byName (Just remotename) >>= \case Just clusterremote -> Remote.byName (Just remotename) >>= \case
Just gatewayremote -> Just gatewayremote ->
case mkClusterUUID (Remote.uuid clusterremote) of case mkClusterUUID (Remote.uuid clusterremote) of
Just cu -> commandAction $ start cu clustername gatewayremote Just cu -> do
commandAction $ start cu clustername gatewayremote
Command.UpdateCluster.seek []
Nothing -> giveup $ clusterremotename Nothing -> giveup $ clusterremotename
++ " is not a cluster remote." ++ " is not a cluster remote."
Nothing -> giveup $ "No remote named " ++ remotename ++ " exists." Nothing -> giveup $ "No remote named " ++ remotename ++ " exists."

1
doc/clusters.mdwn
View file

@ -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 remote add NYC me@nyc.example.com:annex
AMS$ git-annex sync NYC AMS$ git-annex sync NYC
NYC$ git-annex extendcluster NYC mycluster 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 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`. to the entire cluster as either `AMS-mycluster` or `NYC-mycluster`.

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

@ -17,8 +17,12 @@ The `clustername` parameter is the name of the cluster.
The next step after running this command is to configure The next step after running this command is to configure
any additional cluster nodes that this gateway serves to the cluster, any additional cluster nodes that this gateway serves to the cluster,
then run [[git-annex-updatecluster]] on each gateway. then run [[git-annex-updatecluster]]. See the documentation of that
See the documentation of that command for details about configuring nodes. 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 # OPTIONS