From acb45ed9350142e0bd6651292b4f805156d1b971 Mon Sep 17 00:00:00 2001 From: D B <dbeberman@prasaga.com> Date: Mon, 24 Mar 2025 20:18:57 +0000 Subject: [PATCH] Update file readme.md --- readme.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/readme.md b/readme.md index 187bc5c..5c0a253 100644 --- a/readme.md +++ b/readme.md @@ -263,7 +263,7 @@ It is recommended to not hardcode these, use an appropriate host command to retr Deploying the configs and databases After completing configuring the hosts and nodes files, and editing the docker-sagachain-node.sh file, the sagachain-manager.sh may be used to copy the directories to the target machines using scp: -> configs/sagachain-manager.sh \<blockchain name\> scp -r \<blockchain name\> \<blockchain name\> +> \<install dir\>/configs/sagachain-manager.sh \<blockchain name\> scp -r \<blockchain name\> \<blockchain name\> The first parameter to sagachain-manager.sh is always the blockchain name. The second is one of start, stop, start-debug, scp, and several others. Please refer to the case statement in the bash script for the commands. The scp utility takes two directories, the source and destination. In this case it copies the configuration directories from the source machine to all of the target machines. @@ -282,13 +282,13 @@ To create a network with this machine as the designated network manager. It ret On each of the other host machines. Note: there is a general “cmd†command for sagachain-manager.sh available: -> configs/sagachain-manager.sh \<blockchain name\> cmd docker swarm join –token \<…\> \<ip address\>:2377 +> \<install dir\>/configs/sagachain-manager.sh \<blockchain name\> cmd docker swarm join --token \<…\> \<ip address\>:2377 # Launching the Blockchain The sagachain-manager.sh will start the blockchain by downloading the sagachain Node image from hub.docker.com and execute each of the instances on the configured host machines with the appropriate sagachainnodeXX.yaml configuration file. As part of the initial launch sagachain-manager creates a temporary directory: saganodetmp-\<blockchainname\> and makes a copy of the configuration files and the sagachainnodeXX.yaml files used on each host machine. -> configs/sagachain-manager.sh \<blockchain name\> start sagachain/node:v1.0.0 +> \<install dir\>/configs/sagachain-manager.sh \<blockchain name\> start sagachain/node:v1.0.0 The start command takes 4 additional parameters with are TCP port numbers. The docker bridge configuration uses port numbers to distinguish between instances. The port numbers used for each instance are output as part of the start command. The start command copies the configuration from the \<blockchain name\> directories to the saganodetmp-\<blockchain-name\> directories for each run. A separate command, start-debug will reuse the configuration files in the saganodetmp-\<blockchain-name\>. This is useful for enabling various log tracing parameters for a Node instance. -- GitLab