Update nano test network #675
Conversation
|
Note: currently in draft until the ccaas builder is published hyperledger/fabric#3286 |
jt-nti
force-pushed
the
nano-docker
branch
5 times, most recently
from
d1ec79e
to
5526a3e
Compare
test-network-nano-bash/README.md
Outdated
| @@ -120,7 +131,7 @@ export CHAINCODE_SERVER_ADDRESS=127.0.0.1:9999 | |||
| And start the chaincode service: | |||
|
|
|||
| ``` | |||
| npm run start:server-notls | |||
| npm run start:server-nontls | |||
There was a problem hiding this comment.
Hi @timo-kang, the correct script is start:server-nontls so there is currently a typo in the test-network-nano-bash readme. I included the fix in this draft PR but it might be better to fix sooner since it's not really related to the other changes here.
|
@jt-nti can this be un-drafted and moved forward? Do we have the builders now as part of the release archives? |
|
@jkneubuh not yet- there hasn't been a release with the ccaas builder binaries in the release tarballs. Hopefully soon. |
jt-nti
force-pushed
the
nano-docker
branch
6 times, most recently
from
706c650
to
cd1df3e
Compare
Add an option to run the network in a single container Signed-off-by: James Taylor <jamest@uk.ibm.com> # Conflicts: # test-network-nano-bash/README.md
|
The intent of test network nano bash was to have a minimal sample that can be run on local machine without docker layers to complicate things. For docker options, there is the traditional test-network and microfab. I'll go ahead and close. |
Fix minor bugs, add network.sh script to simplify standing up the network, and add an option to run the network in a single container
Note: the updated peerNadmin.sh scripts no longer create or join a channel and now only configure the environment for the relevant peer
Signed-off-by: James Taylor jamest@uk.ibm.com