Skip to content

Commit

Permalink
[FAB-15716] Fix instructions for dev-mode
Browse files Browse the repository at this point in the history
This patch fixes the instructions for dev-mode.

For the commands to start the chaincode to work properly,
this patch modifies the commands.
- Use peer.address flag (instead of the unused env var after FAB-14770)
- Add CORE_PEER_TLS_ENABLED=false (dev-mode is for non-TLS mode only)

FAB-15716 #done

Signed-off-by: Tatsuya Sato <Tatsuya.Sato@hal.hitachi.com>
Change-Id: I160d22389bb611c5b96ee880497266f06d25abd7
  • Loading branch information
satota2 authored and Tatsuya Sato committed Jul 3, 2019
1 parent 0254d67 commit 8bbdd0f
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion chaincode-docker-devmode/README.rst
Original file line number Diff line number Diff line change
Expand Up @@ -69,6 +69,8 @@ one for the chaincode environment and a CLI to interact with the chaincode. The
commands for create and join channel are embedded in the CLI container, so we
can jump immediately to the chaincode calls.

.. note:: TLS is not enabled as it is not supported when running chaincode in dev mode.

Terminal 2 - Build & start the chaincode
----------------------------------------

Expand All @@ -93,7 +95,7 @@ Now run the chaincode:

.. code:: bash
CORE_PEER_ADDRESS=peer:7052 CORE_CHAINCODE_ID_NAME=mycc:0 ./abstore
CORE_CHAINCODE_ID_NAME=mycc:0 CORE_PEER_TLS_ENABLED=false ./abstore -peer.address peer:7052
The chaincode is started with peer and chaincode logs indicating successful registration with the peer.
Note that at this stage the chaincode is not associated with any channel. This is done in subsequent steps
Expand Down

0 comments on commit 8bbdd0f

Please sign in to comment.