@@ -53,15 +53,20 @@ Below is the script's help text.
53
53
```
54
54
startFPCAuctionNetwork.sh [options]
55
55
56
- This script, by default, will teardown possible previous iterations of this demo, generate new
57
- crypto material for the network, start an FPC network as defined in $FPC_PATH/utils/docker-compose,
58
- install the mock golang auction chaincode($FPC_PATH/demo/chaincode/golang), install the FPC
59
- compliant auction chaincode($FPC_PATH/demo/chaincode/fpc), register auction users, and bring up
60
- both the fabric-gatway & frontend UI. If the fabric-gateway and frontend UI docker images have
61
- not previously been built it will build them, otherwise the script will reuse the images already
62
- existing. The FPC chaincode will not be built unless specified by the flag --build-cc.
63
- By calling the script with both build options, you will be able to run the demo without having
64
- to build the whole FPC project (e.g., by calling `make` in $FPC_PATH).
56
+ This script, by default, will teardown possible previous iterations of this
57
+ demo, generate new crypto material for the network, start an FPC network as
58
+ defined in \$FPC_PATH/utils/docker-compose, install the mock golang auction
59
+ chaincode(\$FPC_PATH/demo/chaincode/golang), install the FPC compliant
60
+ auction chaincode(\$FPC_PATH/demo/chaincode/fpc), register auction users,
61
+ and bring up both the fabric-gatway & frontend UI.
62
+
63
+ If the fabric-gateway and frontend UI docker images have not previously been
64
+ built it will build them, otherwise the script will reuse the images already
65
+ existing. You can force a rebuild, though, by specifying the flag
66
+ --build-client. The FPC chaincode will not be built unless specified by the
67
+ flag --build-cc. By calling the script with both build options, you will be
68
+ able to run the demo without having to build the whole FPC project (e.g., by
69
+ calling `make` in $FPC_PATH).
65
70
66
71
options:
67
72
--build-cc:
@@ -95,8 +100,10 @@ will delete all the unused volumes and chaincode images.
95
100
96
101
### Scripting
97
102
98
- To facilitate demonstrations and also to help in testing, you can specify a scenario script defining the
99
- actions of the different parties and execute it using the command [ scenario-run.sh] ( client/scripting/scenario-run.sh ) .
103
+ To facilitate demonstrations and also to help in testing, you can specify with a simple
104
+ [ DSL] ( client/scripting/lib/dsl.sh ) a scenario script defining the
105
+ actions of the different parties and execute it using the command
106
+ [ scenario-run.sh] ( client/scripting/scenario-run.sh ) .
100
107
Below is the script's help text.
101
108
```
102
109
scenario-run.sh [--help|-h|-?] [--bootstrap|-b] [--dry-run|-d] [--non-interactive|-n] [--skip-delay|-s] [--mock-reset|-r] <script-file>
0 commit comments