 Hyperledger Fabric 2.0 Documentationchaincode definition according to the default policy. When committing a channel definition, you need to target enough peer organizations in the channel to satisfy your LifecycleEndorsement policy. You can learn chaincode requires the transaction to be signed by Org1 and Org2, the chaincode invoke command needs to target both peer0.org1.example.com and peer0.org2.example.com using the -- peerAddresses flag. Because eventSource: true peers: peer1.magnetocorp.com: url: grpcs://localhost:7051 grpcOptions: ssl-target-name-override: peer1.magnetocorp.com request-timeout: 120 tlsCACerts: path: certifi0 码力 | 821 页 | 10.22 MB | 1 年前3 Hyperledger Fabric 2.0 Documentationchaincode definition according to the default policy. When committing a channel definition, you need to target enough peer organizations in the channel to satisfy your LifecycleEndorsement policy. You can learn chaincode requires the transaction to be signed by Org1 and Org2, the chaincode invoke command needs to target both peer0.org1.example.com and peer0.org2.example.com using the -- peerAddresses flag. Because eventSource: true peers: peer1.magnetocorp.com: url: grpcs://localhost:7051 grpcOptions: ssl-target-name-override: peer1.magnetocorp.com request-timeout: 120 tlsCACerts: path: certifi0 码力 | 821 页 | 10.22 MB | 1 年前3
 Hyperledger Fabric 2.2.1 Documentationchaincode definition according to the default policy. When committing a channel definition, you need to target enough peer organizations in the channel to satisfy your LifecycleEndorsement policy. You can learn chaincode requires the transaction to be signed by Org1 and Org2, the chaincode invoke command needs to target both peer0.org1.example.com and peer0.org2.example. com using the --peerAddresses flag. Because TLS true eventSource: true peers: peer1.magnetocorp.com: url: grpcs://localhost:7051 grpcOptions: ssl-target-name-override: peer1.magnetocorp.com request-timeout: 120 tlsCACerts: (continues on next page)0 码力 | 575 页 | 8.55 MB | 1 年前3 Hyperledger Fabric 2.2.1 Documentationchaincode definition according to the default policy. When committing a channel definition, you need to target enough peer organizations in the channel to satisfy your LifecycleEndorsement policy. You can learn chaincode requires the transaction to be signed by Org1 and Org2, the chaincode invoke command needs to target both peer0.org1.example.com and peer0.org2.example. com using the --peerAddresses flag. Because TLS true eventSource: true peers: peer1.magnetocorp.com: url: grpcs://localhost:7051 grpcOptions: ssl-target-name-override: peer1.magnetocorp.com request-timeout: 120 tlsCACerts: (continues on next page)0 码力 | 575 页 | 8.55 MB | 1 年前3
 Hyperledger Fabric 2.1.1 Documentationchaincode definition according to the default policy. When committing a channel definition, you need to target enough peer organizations in the channel to satisfy your LifecycleEndorsement policy. You can learn chaincode requires the transaction to be signed by Org1 and Org2, the chaincode invoke command needs to target both peer0.org1.example.com and peer0.org2.example.com using the -- peerAddresses flag. Because TLS eventSource: true peers: peer1.magnetocorp.com: url: grpcs://localhost:7051 grpcOptions: ssl-target-name-override: peer1.magnetocorp.com request-timeout: 120 tlsCACerts: path: certifi0 码力 | 816 页 | 10.25 MB | 1 年前3 Hyperledger Fabric 2.1.1 Documentationchaincode definition according to the default policy. When committing a channel definition, you need to target enough peer organizations in the channel to satisfy your LifecycleEndorsement policy. You can learn chaincode requires the transaction to be signed by Org1 and Org2, the chaincode invoke command needs to target both peer0.org1.example.com and peer0.org2.example.com using the -- peerAddresses flag. Because TLS eventSource: true peers: peer1.magnetocorp.com: url: grpcs://localhost:7051 grpcOptions: ssl-target-name-override: peer1.magnetocorp.com request-timeout: 120 tlsCACerts: path: certifi0 码力 | 816 页 | 10.25 MB | 1 年前3
 Hyperledger Fabric 2.0 Documentationchaincode definition according to the default policy. When committing a channel definition, you need to target enough peer organizations in the channel to satisfy your LifecycleEndorsement policy. You can learn chaincode requires the transaction to be signed by Org1 and Org2, the chaincode invoke command needs to target both peer0.org1.example.com and peer0.org2.example. com using the --peerAddresses flag. Because TLS true eventSource: true peers: peer1.magnetocorp.com: url: grpcs://localhost:7051 grpcOptions: ssl-target-name-override: peer1.magnetocorp.com request-timeout: 120 tlsCACerts: (continues on next page)0 码力 | 573 页 | 8.52 MB | 1 年前3 Hyperledger Fabric 2.0 Documentationchaincode definition according to the default policy. When committing a channel definition, you need to target enough peer organizations in the channel to satisfy your LifecycleEndorsement policy. You can learn chaincode requires the transaction to be signed by Org1 and Org2, the chaincode invoke command needs to target both peer0.org1.example.com and peer0.org2.example. com using the --peerAddresses flag. Because TLS true eventSource: true peers: peer1.magnetocorp.com: url: grpcs://localhost:7051 grpcOptions: ssl-target-name-override: peer1.magnetocorp.com request-timeout: 120 tlsCACerts: (continues on next page)0 码力 | 573 页 | 8.52 MB | 1 年前3
 Hyperledger Fabric 2.2.1 Documentationchaincode definition according to the default policy. When committing a channel definition, you need to target enough peer organizations in the channel to satisfy your LifecycleEndorsement policy. You can learn chaincode requires the transaction to be signed by Org1 and Org2, the chaincode invoke command needs to target both peer0.org1.example.com and peer0.org2.example.com using the --peerAddresses flag. Because TLS eventSource: true peers: peer1.magnetocorp.com: url: grpcs://localhost:7051 grpcOptions: ssl-target-name-override: peer1.magnetocorp.com request-timeout: 120 tlsCACerts: path: certifi0 码力 | 848 页 | 11.56 MB | 1 年前3 Hyperledger Fabric 2.2.1 Documentationchaincode definition according to the default policy. When committing a channel definition, you need to target enough peer organizations in the channel to satisfy your LifecycleEndorsement policy. You can learn chaincode requires the transaction to be signed by Org1 and Org2, the chaincode invoke command needs to target both peer0.org1.example.com and peer0.org2.example.com using the --peerAddresses flag. Because TLS eventSource: true peers: peer1.magnetocorp.com: url: grpcs://localhost:7051 grpcOptions: ssl-target-name-override: peer1.magnetocorp.com request-timeout: 120 tlsCACerts: path: certifi0 码力 | 848 页 | 11.56 MB | 1 年前3
 Hyperledger Fabric 2.1 Documentationchaincode definition according to the default policy. When committing a channel definition, you need to target enough peer organizations in the channel to satisfy your LifecycleEndorsement policy. You can learn chaincode requires the transaction to be signed by Org1 and Org2, the chaincode invoke command needs to target both peer0.org1.example.com and peer0.org2.example.com using the -- peerAddresses flag. Because TLS eventSource: true peers: peer1.magnetocorp.com: url: grpcs://localhost:7051 grpcOptions: ssl-target-name-override: peer1.magnetocorp.com request-timeout: 120 tlsCACerts: path: certifi0 码力 | 904 页 | 10.95 MB | 1 年前3 Hyperledger Fabric 2.1 Documentationchaincode definition according to the default policy. When committing a channel definition, you need to target enough peer organizations in the channel to satisfy your LifecycleEndorsement policy. You can learn chaincode requires the transaction to be signed by Org1 and Org2, the chaincode invoke command needs to target both peer0.org1.example.com and peer0.org2.example.com using the -- peerAddresses flag. Because TLS eventSource: true peers: peer1.magnetocorp.com: url: grpcs://localhost:7051 grpcOptions: ssl-target-name-override: peer1.magnetocorp.com request-timeout: 120 tlsCACerts: path: certifi0 码力 | 904 页 | 10.95 MB | 1 年前3
 Hyperledger Fabric 2.5 中文文档present once. However, this prevents explicit/intentional running of a task multiple times on the same target host, which is sometimes useful. To turn off deduplication, set env.dedupe_hosts to False. Excluding host lists A common intermediate-to-advanced use case for Fabric is to parameterize lookup of one’s target host list at runtime (when use of Roles does not suffice). execute can make this extremely simple context_managers.remote_tunnel(*args, **kwds) Create a tunnel forwarding a locally-visible port to the remote target. For example, you can let the remote host access a database that is installed on the client host:0 码力 | 138 页 | 154.00 KB | 1 年前3 Hyperledger Fabric 2.5 中文文档present once. However, this prevents explicit/intentional running of a task multiple times on the same target host, which is sometimes useful. To turn off deduplication, set env.dedupe_hosts to False. Excluding host lists A common intermediate-to-advanced use case for Fabric is to parameterize lookup of one’s target host list at runtime (when use of Roles does not suffice). execute can make this extremely simple context_managers.remote_tunnel(*args, **kwds) Create a tunnel forwarding a locally-visible port to the remote target. For example, you can let the remote host access a database that is installed on the client host:0 码力 | 138 页 | 154.00 KB | 1 年前3
 Hyperledger Fabric 2.2.0 Documentationchaincode definition according to the default policy. When committing a channel definition, you need to target enough peer organizations in the channel to satisfy your LifecycleEndorsement policy. You can learn chaincode requires the transaction to be signed by Org1 and Org2, the chaincode invoke command needs to target both peer0.org1.example.com and peer0.org2.example. com using the --peerAddresses flag. Because TLS true eventSource: true peers: peer1.magnetocorp.com: url: grpcs://localhost:7051 grpcOptions: ssl-target-name-override: peer1.magnetocorp.com request-timeout: 120 tlsCACerts: (continues on next page)0 码力 | 577 页 | 9.03 MB | 1 年前3 Hyperledger Fabric 2.2.0 Documentationchaincode definition according to the default policy. When committing a channel definition, you need to target enough peer organizations in the channel to satisfy your LifecycleEndorsement policy. You can learn chaincode requires the transaction to be signed by Org1 and Org2, the chaincode invoke command needs to target both peer0.org1.example.com and peer0.org2.example. com using the --peerAddresses flag. Because TLS true eventSource: true peers: peer1.magnetocorp.com: url: grpcs://localhost:7051 grpcOptions: ssl-target-name-override: peer1.magnetocorp.com request-timeout: 120 tlsCACerts: (continues on next page)0 码力 | 577 页 | 9.03 MB | 1 年前3
 Hyperledger Fabric 2.2.0 Documentationchaincode definition according to the default policy. When committing a channel definition, you need to target enough peer organizations in the channel to satisfy your LifecycleEndorsement policy. You can learn chaincode requires the transaction to be signed by Org1 and Org2, the chaincode invoke command needs to target both peer0.org1.example.com and peer0.org2.example.com using the -- peerAddresses flag. Because TLS eventSource: true peers: peer1.magnetocorp.com: url: grpcs://localhost:7051 grpcOptions: ssl-target-name-override: peer1.magnetocorp.com request-timeout: 120 tlsCACerts: path: certifi0 码力 | 820 页 | 10.90 MB | 1 年前3 Hyperledger Fabric 2.2.0 Documentationchaincode definition according to the default policy. When committing a channel definition, you need to target enough peer organizations in the channel to satisfy your LifecycleEndorsement policy. You can learn chaincode requires the transaction to be signed by Org1 and Org2, the chaincode invoke command needs to target both peer0.org1.example.com and peer0.org2.example.com using the -- peerAddresses flag. Because TLS eventSource: true peers: peer1.magnetocorp.com: url: grpcs://localhost:7051 grpcOptions: ssl-target-name-override: peer1.magnetocorp.com request-timeout: 120 tlsCACerts: path: certifi0 码力 | 820 页 | 10.90 MB | 1 年前3
 Hyperledger Fabric 1.4 中文文档present once. However, this prevents explicit/intentional running of a task multiple times on the same target host, which is sometimes useful. To turn off deduplication, set env.dedupe_hosts to False. Excluding host lists A common intermediate-to-advanced use case for Fabric is to parameterize lookup of one’s target host list at runtime (when use of Roles does not suffice). execute can make this extremely simple context_managers.remote_tunnel(*args, **kwds) Create a tunnel forwarding a locally-visible port to the remote target. For example, you can let the remote host access a database that is installed on the client host:0 码力 | 145 页 | 161.53 KB | 1 年前3 Hyperledger Fabric 1.4 中文文档present once. However, this prevents explicit/intentional running of a task multiple times on the same target host, which is sometimes useful. To turn off deduplication, set env.dedupe_hosts to False. Excluding host lists A common intermediate-to-advanced use case for Fabric is to parameterize lookup of one’s target host list at runtime (when use of Roles does not suffice). execute can make this extremely simple context_managers.remote_tunnel(*args, **kwds) Create a tunnel forwarding a locally-visible port to the remote target. For example, you can let the remote host access a database that is installed on the client host:0 码力 | 145 页 | 161.53 KB | 1 年前3
共 69 条
- 1
- 2
- 3
- 4
- 5
- 6
- 7














