- The command to get logs from container is
docker logs -f <container_name for peers and orderer>
-
The Chaincode Invoke command is read like this,
- orderer: orderer.example.com (and its TLS root certificate)
- channel name: mychannel
- chaincode name: fabcar endorsing peers:
- peer0.org1.example.com and peer0.org2.example.com (and their TLS root certificates)
- arguments: [“createCar”, “CAR12”, “Honda”, “Accord”, “black”, “Tom”]
docker exec cli peer chaincode invoke -o orderer.example.com:7050 --tls true --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem -C mychannel -n fabcar --peerAddresses peer0.org1.example.com:7051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/tls/ca.crt --peerAddresses peer0.org2.example.com:9051 --tlsRootCertFiles /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org2.example.com/peers/peer0.org2.example.com/tls/ca.crt -c ‘{“Args”:[“createCar”, “CAR12”, “Honda”, “Accord”, “black”, “Tom”]}’
3. Lifecycle chaincode
- Package chaincode
- Install chaincode package on selected peers in
- each organization Approve chaincode definition for each organization
- Commit chaincode definition to channel when lifecycle endorsement policy is satisfied
前 3 步分別完成，可互不干擾，甚至合約內容不是完全相同（但大概邏輯需一直，或者說一部分邏輯是相同的，否則這個 consortium 也是無意義的）。
比如 sacc ，sacc-age（比 sacc 多了一句判斷， 68-70）
