@@ -49,28 +49,38 @@ Here's the help text for the ``byfn.sh`` script:
49
49
50
50
.. code :: bash
51
51
52
- ./byfn.sh --help
53
52
Usage:
54
- byfn.sh up| down| restart| generate [-c < channel name> ] [-t < timeout> ] [-d < delay> ] [-f < docker-compose-file> ] [-s < dbtype> ]
55
- byfn.sh -h| --help (print this message)
56
- -m < mode> - one of ' up' , ' down' , ' restart' or ' generate'
57
- - ' up' - bring up the network with docker-compose up
58
- - ' down' - clear the network with docker-compose down
59
- - ' restart' - restart the network
60
- - ' generate' - generate required certificates and genesis block
61
- -c < channel name> - channel name to use (defaults to " mychannel" )
62
- -t < timeout> - CLI timeout duration in seconds (defaults to 10)
63
- -d < delay> - delay duration in seconds (defaults to 3)
64
- -f < docker-compose-file> - specify which docker-compose file use (defaults to docker-compose-cli.yaml)
65
- -s < dbtype> - the database backend to use: goleveldb (default) or couchdb
66
- -l < language> - the chaincode language: golang (default) or node
67
- -a - don' t ask for confirmation before proceeding
68
-
69
- Typically, one would first generate the required certificates and
70
- genesis block, then bring up the network. e.g.:
71
-
72
- byfn.sh -m generate -c mychannel
73
- byfn.sh -m up -c mychannel -s couchdb
53
+ byfn.sh < mode> [-c < channel name> ] [-t < timeout> ] [-d < delay> ] [-f < docker-compose-file> ] [-s < dbtype> ] [-l < language> ] [-i < imagetag> ] [-v]
54
+ < mode> - one of ' up' , ' down' , ' restart' , ' generate' or ' upgrade'
55
+ - ' up' - bring up the network with docker-compose up
56
+ - ' down' - clear the network with docker-compose down
57
+ - ' restart' - restart the network
58
+ - ' generate' - generate required certificates and genesis block
59
+ - ' upgrade' - upgrade the network from v1.0.x to v1.1
60
+ -c < channel name> - channel name to use (defaults to " mychannel" )
61
+ -t < timeout> - CLI timeout duration in seconds (defaults to 10)
62
+ -d < delay> - delay duration in seconds (defaults to 3)
63
+ -f < docker-compose-file> - specify which docker-compose file use (defaults to docker-compose-cli.yaml)
64
+ -s < dbtype> - the database backend to use: goleveldb (default) or couchdb
65
+ -l < language> - the chaincode language: golang (default) or node
66
+ -i < imagetag> - the tag to be used to launch the network (defaults to " latest" )
67
+ -v - verbose mode
68
+ byfn.sh -h (print this message)
69
+
70
+ Typically, one would first generate the required certificates and
71
+ genesis block, then bring up the network. e.g.:
72
+
73
+ byfn.sh generate -c mychannel
74
+ byfn.sh up -c mychannel -s couchdb
75
+ byfn.sh up -c mychannel -s couchdb -i 1.1.0-alpha
76
+ byfn.sh up -l node
77
+ byfn.sh down -c mychannel
78
+ byfn.sh upgrade -c mychannel
79
+
80
+ Taking all defaults:
81
+ byfn.sh generate
82
+ byfn.sh up
83
+ byfn.sh down
74
84
75
85
If you choose not to supply a channel name, then the
76
86
script will use a default name of ``mychannel ``. The CLI timeout parameter
@@ -85,7 +95,7 @@ Ready to give it a go? Okay then! Execute the following command:
85
95
86
96
.. code :: bash
87
97
88
- ./byfn.sh -m generate
98
+ ./byfn.sh generate
89
99
90
100
You will see a brief description as to what will occur, along with a yes/no command line
91
101
prompt. Respond with a ``y `` or hit the return key to execute the described action.
@@ -147,7 +157,7 @@ Next, you can bring the network up with one of the following commands:
147
157
148
158
.. code :: bash
149
159
150
- ./byfn.sh -m up
160
+ ./byfn.sh up
151
161
152
162
The above command will compile Golang chaincode images and spin up the corresponding
153
163
containers. Go is the default chaincode language, however there is also support
@@ -159,7 +169,7 @@ chaincode, pass the following command instead:
159
169
# we use the -l flag to specify the chaincode language
160
170
# forgoing the -l flag will default to Golang
161
171
162
- ./byfn.sh -m up -l node
172
+ ./byfn.sh up -l node
163
173
164
174
.. note :: View the `Hyperledger Fabric Shim <https://fabric-shim.github.io/ChaincodeStub.html>`__
165
175
documentation for more info on the node.js chaincode shim APIs.
@@ -222,7 +232,7 @@ and four artifacts, and delete the chaincode images from your Docker Registry:
222
232
223
233
.. code :: bash
224
234
225
- ./byfn.sh -m down
235
+ ./byfn.sh down
226
236
227
237
Once again, you will be prompted to continue, respond with a ``y `` or hit the return key:
228
238
@@ -1083,7 +1093,7 @@ Troubleshooting
1083
1093
1084
1094
.. code :: bash
1085
1095
1086
- ./byfn.sh -m down
1096
+ ./byfn.sh down
1087
1097
1088
1098
.. note :: You **will** see errors if you do not remove old containers
1089
1099
and images.
@@ -1146,7 +1156,7 @@ Troubleshooting
1146
1156
1147
1157
.. code :: bash
1148
1158
1149
- ./byfn.sh -m down
1159
+ ./byfn.sh down
1150
1160
1151
1161
- If you see an error stating that you still have "active endpoints", then prune
1152
1162
your Docker networks. This will wipe your previous networks and start you with a
0 commit comments