国产无码综合区,色欲AV无码国产永久播放,无码天堂亚洲国产AV,国产日韩欧美女同一区二区

<tr id="lzpgu"><small id="lzpgu"><em id="lzpgu"></em></small></tr>

<track id="lzpgu"></track>

<tr id="lzpgu"><form id="lzpgu"><em id="lzpgu"></em></form></tr>

^{<track id="lzpgu"><xmp id="lzpgu"></xmp></track>}

hyperledger fabric 網(wǎng)絡(luò)操作基本操作和概念

2年前作者：計(jì)劃是動(dòng)力分類：Toy博客閱讀(28)違法舉報(bào)

這篇具有很好參考價(jià)值的文章主要介紹了hyperledger fabric 網(wǎng)絡(luò)操作基本操作和概念。希望對大家有所幫助。如果存在錯(cuò)誤或未考慮完全的地方，請大家不吝賜教，您也可以點(diǎn)擊"舉報(bào)違法"按鈕提交疑問。

hyperledger fabric 網(wǎng)絡(luò)操作基本操作和概念

在搭建好hyperledger fabric環(huán)境后，繼續(xù)進(jìn)行網(wǎng)絡(luò)搭建操作
新建文件夾twonodes（與github.com同級(jí)）

1. cryptogen 操作

1.1 cryptogen 生成證書文件

1.1.1 生成證書文件模板

# 打印模板到終端
cryptogen showtemplate
# 打印模板到配置文件crypto-config.yaml
cryptogen showtemplate > crypto-config.yaml

生成模板配置文件說明

1.1.1.1 排序節(jié)點(diǎn)OrdererOrgs配置

OrdererOrgs:
  - Name: Orderer # 排序節(jié)點(diǎn)名稱
    Domain: example.com # 排序節(jié)點(diǎn)域名
    EnableNodeOUs: false # 是否使用OU配置(OU表示組織單元即每個(gè)組織下面很多節(jié)點(diǎn)，可以將一些節(jié)點(diǎn)作為一個(gè)部門)
    # "Specs" - See PeerOrgs below for complete description
    Specs:
      - Hostname: orderer

1.1.1.2 普通節(jié)點(diǎn)PeerOrgs配置

PeerOrgs:
  # Org1 組織1
  - Name: Org1 #組織1名稱
    Domain: org1.example.com #組織1域名
    EnableNodeOUs: true

1.1.1.3 Template 配置

Template:
      Count: 1 # 組織節(jié)點(diǎn)個(gè)數(shù)，節(jié)點(diǎn)名稱順序排列
      # Start: 5
      # Hostname: {{.Prefix}}{{.Index}} # default
      # SANS:
      #   - "{{.Hostname}}.alt.{{.Domain}}"

    #

1.1.1.4 Users用戶配置

(user和peer區(qū)別，user可以理解為終端，指人，而peer是節(jié)點(diǎn)，只是一臺(tái)運(yùn)行的機(jī)器或集群的一個(gè)節(jié)點(diǎn))

    # "Users"
    # Count: The number of user accounts _in addition_ to Admin
    Users:
      Count: 1

1.1.1.5 crypto-config.yaml

Order組織節(jié)點(diǎn)定義

OrdererOrgs:
  # ---------------------------------------------------------------------------
  # Orderer
  # ---------------------------------------------------------------------------
  - Name: Orderer
    Domain: trace.com
    Specs:
      - Hostname: orderer

PeerOrgs:
  # ---------------------------------------------------------------------------
  # Org1
  # ---------------------------------------------------------------------------
  - Name: Org1
    Domain: org1.trace.com
    Template:
      Count: 1
    Users:
      Count: 1
 # ---------------------------------------------------------------------------
  # Org2
  # ---------------------------------------------------------------------------
  - Name: Org2
    Domain: org2.trace.com
    Template:
      Count: 1
    Users:
      Count: 1
 # ---------------------------------------------------------------------------
  # Org3
  # ---------------------------------------------------------------------------
  - Name: Org3
    Domain: org3.trace.com
    Template:
      Count: 1
    Users:
      Count: 1
 # ---------------------------------------------------------------------------
  # Org4
  # ---------------------------------------------------------------------------
  - Name: Org4
    Domain: org4.trace.com
    Template:
      Count: 1
    Users:
      Count: 1

# ---------------------------------------------------------------------------
  # Org5
  # ---------------------------------------------------------------------------
  - Name: Org5
    Domain: org5.trace.com
    Template:
      Count: 1
    Users:
      Count: 1

1.1.2 生成密鑰材料

cryptogen generate --config=crypto-config.yaml

hyperledger fabric網(wǎng)絡(luò)操作基本操作和概念,深入探索hyperledger fabric聯(lián)盟鏈搭建,fabric,網(wǎng)絡(luò),區(qū)塊鏈

1.2 cryptogen.yaml 創(chuàng)建通道配置

拷貝/hyperledger/fabric-samples/test-network/configtx/configx.yaml 到目錄下
修改msp配置文件（成員服務(wù)提供者 (MSP)及相關(guān)證書配置
因?yàn)镕abric是一個(gè)認(rèn)證性的網(wǎng)絡(luò), 所以區(qū)塊鏈參與者需要一種向網(wǎng)絡(luò)中的其他參與者證實(shí)自己身份的機(jī)制從而在網(wǎng)絡(luò)中進(jìn)行交易
證書機(jī)構(gòu)通過生成可以用來證實(shí)身份的由公鑰和私鑰形成的鍵值對來發(fā)放認(rèn)證信息。因?yàn)橐粋€(gè)私鑰永遠(yuǎn)不會(huì)被公開，所以引入了一種可以證實(shí)身份的機(jī)制即MSP。例如，一個(gè)peer節(jié)點(diǎn)用它的私鑰進(jìn)行數(shù)字簽名或背書交易。接著排序節(jié)點(diǎn)包含的該peer節(jié)點(diǎn)的公鑰會(huì)被用來驗(yàn)證交易攜帶的簽名是否合法。私鑰被用作生成交易信息上的，只有與私鑰相對應(yīng)的且作為MSP一部分的公鑰可以匹配的簽名。因此，MSP是一個(gè)可讓身份被信任和被網(wǎng)絡(luò)中其他參與者公認(rèn)的，而不需要暴露成員的私鑰的機(jī)制。

MSPDir: ../organizations/ordererOrganizations/example.com/msp
# 改為
MSPDir: crypto-config/ordererOrganizations/example.com/msp

1.2.1 configx.yaml

#
# SPDX-License-Identifier: Apache-2.0
#

---
################################################################################
#
#   Section: Organizations
#
#   - This section defines the different organizational identities which will
#   be referenced later in the configuration.
#
################################################################################
Organizations:

    # SampleOrg defines an MSP using the sampleconfig.  It should never be used
    # in production but may be used as a template for other definitions
    - &OrdererOrg
        # DefaultOrg defines the organization which is used in the sampleconfig
        # of the fabric.git development environment
        Name: OrdererOrg

        # ID to load the MSP definition as
        ID: OrdererMSP

        # MSPDir is the filesystem path which contains the MSP configuration
        MSPDir: crypto-config/ordererOrganizations/trace.com/msp

    - &Org1
        # DefaultOrg defines the organization which is used in the sampleconfig
        # of the fabric.git development environment
        Name: Org1MSP

        # ID to load the MSP definition as
        ID: Org1MSP

        MSPDir: crypto-config/peerOrganizations/org1.trace.com/msp

        AnchorPeers:
            # AnchorPeers defines the location of peers which can be used
            # for cross org gossip communication.  Note, this value is only
            # encoded in the genesis block in the Application section context
            - Host: peer0.org1.trace.com
              Port: 7051

    - &Org2
        # DefaultOrg defines the organization which is used in the sampleconfig
        # of the fabric.git development environment
        Name: Org2MSP

        # ID to load the MSP definition as
        ID: Org2MSP

        MSPDir: crypto-config/peerOrganizations/org2.trace.com/msp

        AnchorPeers:
            # AnchorPeers defines the location of peers which can be used
            # for cross org gossip communication.  Note, this value is only
            # encoded in the genesis block in the Application section context
            - Host: peer0.org2.trace.com
              Port: 7051

    - &Org3
        # DefaultOrg defines the organization which is used in the sampleconfig
        # of the fabric.git development environment
        Name: Org3MSP

        # ID to load the MSP definition as
        ID: Org3MSP

        MSPDir: crypto-config/peerOrganizations/org3.trace.com/msp

        AnchorPeers:
            # AnchorPeers defines the location of peers which can be used
            # for cross org gossip communication.  Note, this value is only
            # encoded in the genesis block in the Application section context
            - Host: peer0.org3.trace.com
              Port: 7051


    - &Org4
        # DefaultOrg defines the organization which is used in the sampleconfig
        # of the fabric.git development environment
        Name: Org4MSP

        # ID to load the MSP definition as
        ID: Org4MSP

        MSPDir: crypto-config/peerOrganizations/org4.trace.com/msp

        AnchorPeers:
            # AnchorPeers defines the location of peers which can be used
            # for cross org gossip communication.  Note, this value is only
            # encoded in the genesis block in the Application section context
            - Host: peer0.org4.trace.com
              Port: 7051

    - &Org5
        # DefaultOrg defines the organization which is used in the sampleconfig
        # of the fabric.git development environment
        Name: Org5MSP

        # ID to load the MSP definition as
        ID: Org5MSP

        MSPDir: crypto-config/peerOrganizations/org5.trace.com/msp

        AnchorPeers:
            # AnchorPeers defines the location of peers which can be used
            # for cross org gossip communication.  Note, this value is only
            # encoded in the genesis block in the Application section context
            - Host: peer0.org5.trace.com
              Port: 7051

################################################################################
#
#   SECTION: Capabilities
#
#   - This section defines the capabilities of fabric network. This is a new
#   concept as of v1.1.0 and should not be utilized in mixed networks with
#   v1.0.x peers and orderers.  Capabilities define features which must be
#   present in a fabric binary for that binary to safely participate in the
#   fabric network.  For instance, if a new MSP type is added, newer binaries
#   might recognize and validate the signatures from this type, while older
#   binaries without this support would be unable to validate those
#   transactions.  This could lead to different versions of the fabric binaries
#   having different world states.  Instead, defining a capability for a channel
#   informs those binaries without this capability that they must cease
#   processing transactions until they have been upgraded.  For v1.0.x if any
#   capabilities are defined (including a map with all capabilities turned off)
#   then the v1.0.x peer will deliberately crash.
#
################################################################################
Capabilities:
    # Channel capabilities apply to both the orderers and the peers and must be
    # supported by both.  Set the value of the capability to true to require it.
    Global: &ChannelCapabilities
        # V1.1 for Global is a catchall flag for behavior which has been
        # determined to be desired for all orderers and peers running v1.0.x,
        # but the modification of which would cause incompatibilities.  Users
        # should leave this flag set to true.
        V1_1: true

    # Orderer capabilities apply only to the orderers, and may be safely
    # manipulated without concern for upgrading peers.  Set the value of the
    # capability to true to require it.
    Orderer: &OrdererCapabilities
        # V1.1 for Order is a catchall flag for behavior which has been
        # determined to be desired for all orderers running v1.0.x, but the
        # modification of which  would cause incompatibilities.  Users should
        # leave this flag set to true.
        V1_1: true

    # Application capabilities apply only to the peer network, and may be safely
    # manipulated without concern for upgrading orderers.  Set the value of the
    # capability to true to require it.
    Application: &ApplicationCapabilities
        # V1.2 for Application is a catchall flag for behavior which has been
        # determined to be desired for all peers running v1.0.x, but the
        # modification of which would cause incompatibilities.  Users should
        # leave this flag set to true.
        V1_2: true

################################################################################
#
#   SECTION: Application
#
#   - This section defines the values to encode into a config transaction or
#   genesis block for application related parameters
#
################################################################################
Application: &ApplicationDefaults

    # Organizations is the list of orgs which are defined as participants on
    # the application side of the network
    Organizations:

################################################################################
#
#   SECTION: Orderer
#
#   - This section defines the values to encode into a config transaction or
#   genesis block for orderer related parameters
#
################################################################################
Orderer: &OrdererDefaults

    # Orderer Type: The orderer implementation to start
    # Available types are "solo" and "kafka"
    OrdererType: solo

    Addresses:
        - orderer.trace.com:7050
    # Batch Timeout: The amount of time to wait before creating a batch
    BatchTimeout: 2s

    # Batch Size: Controls the number of messages batched into a block
    BatchSize:

        # Max Message Count: The maximum number of messages to permit in a batch
        MaxMessageCount: 10

        # Absolute Max Bytes: The absolute maximum number of bytes allowed for
        # the serialized messages in a batch.
        AbsoluteMaxBytes: 99 MB

        # Preferred Max Bytes: The preferred maximum number of bytes allowed for
        # the serialized messages in a batch. A message larger than the preferred
        # max bytes will result in a batch larger than preferred max bytes.
        PreferredMaxBytes: 512 KB

    Kafka:
        # Brokers: A list of Kafka brokers to which the orderer connects
        # NOTE: Use IP:port notation
        Brokers:
            - 127.0.0.1:9092

    # Organizations is the list of orgs which are defined as participants on
    # the orderer side of the network
    Organizations:

################################################################################
#
#   Profile
#
#   - Different configuration profiles may be encoded here to be specified
#   as parameters to the configtxgen tool
#
################################################################################
Profiles:

    FiveOrgsOrdererGenesis:
        Capabilities:
            <<: *ChannelCapabilities
        Orderer:
            <<: *OrdererDefaults
            Organizations:
                - *OrdererOrg
            Capabilities:
                <<: *OrdererCapabilities
        Consortiums:
            SampleConsortium:
                Organizations:
                    - *Org1
                    - *Org2
                    - *Org3
                    - *Org4
                    - *Org5
    FiveOrgsChannel:
        Consortium: SampleConsortium
        Application:
            <<: *ApplicationDefaults
            Organizations:
                - *Org1
                - *Org2
                - *Org3
                - *Org4
                - *Org5
            Capabilities:
                <<: *ApplicationCapabilities

1.3 網(wǎng)絡(luò)初始化

configtxgen -profile SampleMultiNodeEtcdRaft -channelID systemchannel -outputBlock ./channel-artifacts/genesis.block
# 生成系統(tǒng)文件的創(chuàng)世塊
configtxgen -profile Thr eeOrgsChannel -outputCreateChannelTx ./channel-artifacts/channel.tx -channelID testchannel
# 生成用于創(chuàng)建應(yīng)用通道的通道文件
configtxgen -profile ThreeOrgsChannel -outputAnchorPeersUpdate ./channel-artifacts/Org1MSPanchors.tx -channelID appchannel -asOrg Org1MSP
# 生成Org1進(jìn)行錨節(jié)點(diǎn)更新的文件
configtxgen -profile ThreeOrgsChannel -outputAnchorPeersUpdate ./channel-artifacts/Org2MSPanchors.tx -channelID appchannel -asOrg Org2MSP
# 生成Org2進(jìn)行錨節(jié)點(diǎn)更新的文件
configtxgen -profile ThreeOrgsChannel -outputAnchorPeersUpdate ./channel-artifacts/Org3MSPanchors.tx -channelID appchannel -asOrg Org3MSP
# 生成Org3進(jìn)行錨節(jié)點(diǎn)更新的文件

2. docker compose

區(qū)塊鏈docker節(jié)點(diǎn)集群搭建（基于docker compose）

2.1 docker-compose.yaml

#i
# Copyright IBM Corp All Rights Reserved
#
# SPDX-License-Identifier: Apache-2.0
#
version: '2'

volumes:
  orderer.trace.com:
  peer0.org1.trace.com:
  peer0.org2.trace.com:
  peer0.org3.trace.com:
  peer0.org4.trace.com:
  peer0.org5.trace.com:

networks:
  basic:

services:
  ca.trace.com:
    image: hyperledger/fabric-ca
    environment:
      - FABRIC_CA_HOME=/etc/hyperledger/fabric-ca-server
      - FABRIC_CA_SERVER_CA_NAME=ca.trace.com
      - FABRIC_CA_SERVER_CA_CERTFILE=/etc/hyperledger/fabric-ca-server-config/ca.org1.trace.com-cert.pem
      - FABRIC_CA_SERVER_CA_KEYFILE=/etc/hyperledger/fabric-ca-server-config/38495dada2d3a879981547003d601ed405cde661e55e568cce718a6618360d79_sk
      
    ports:
      - 7054:7054
    command: sh -c 'fabric-ca-server start -b admin:adminpw -d'
    volumes:
      - ./crypto-config/peerOrganizations/org1.trace.com/ca/:/etc/hyperledger/fabric-ca-server-config
    container_name: ca.trace.com
    networks:
      - basic

  orderer.trace.com:
    container_name: orderer.trace.com
    image: hyperledger/fabric-orderer
    environment:
      - ORDERER_GENERAL_LOGLEVEL=INFO
      - ORDERER_GENERAL_LISTENADDRESS=0.0.0.0
      - ORDERER_GENERAL_GENESISMETHOD=file
      - ORDERER_GENERAL_GENESISFILE=/var/hyperledger/orderer/orderer.genesis.block
      - ORDERER_GENERAL_LOCALMSPID=OrdererMSP
      - ORDERER_GENERAL_LOCALMSPDIR=/var/hyperledger/orderer/msp
      # enabled TLS
#      - ORDERER_GENERAL_TLS_ENABLED=true
#      - ORDERER_GENERAL_TLS_PRIVATEKEY=/var/hyperledger/orderer/tls/server.key
#      - ORDERER_GENERAL_TLS_CERTIFICATE=/var/hyperledger/orderer/tls/server.crt
#      - ORDERER_GENERAL_TLS_ROOTCAS=[/var/hyperledger/orderer/tls/ca.crt]
    working_dir: /opt/gopath/src/github.com/hyperledger/fabric
    command: orderer
    volumes:
    - ./channel-artifacts/genesis.block:/var/hyperledger/orderer/orderer.genesis.block
    - ./crypto-config/ordererOrganizations/trace.com/orderers/orderer.trace.com/msp:/var/hyperledger/orderer/msp
    - ./crypto-config/ordererOrganizations/trace.com/orderers/orderer.trace.com/tls/:/var/hyperledger/orderer/tls
    - orderer.trace.com:/var/hyperledger/production/orderer
    ports:
      - 7050:7050
    networks:
      - basic


  peer0.org1.trace.com:
    container_name: peer0.org1.trace.com
    image: hyperledger/fabric-peer
    environment:
      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
      - CORE_PEER_ID=peer0.org1.trace.com
      - CORE_LOGGING_PEER=info
      - CORE_CHAINCODE_LOGGING_LEVEL=info
      - CORE_PEER_LOCALMSPID=Org1MSP
      - CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/msp/peer/
      - CORE_PEER_ADDRESS=peer0.org1.trace.com:7051
      # # the following setting starts chaincode containers on the same
      # # bridge network as the peers
      # # https://docs.docker.com/compose/networking/
      - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=basic-network_basic
      - CORE_LEDGER_STATE_STATEDATABASE=CouchDB
      - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb:5984
      # The CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME and CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD
      # provide the credentials for ledger to connect to CouchDB.  The username and password must
      # match the username and password set for the associated CouchDB.
      - CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME=
      - CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD=
      # enabled TLS
#      - CORE_PEER_TLS_ENABLED=true
#      - CORE_PEER_PROFILE_ENABLED=true
#      - CORE_PEER_TLS_CERT_FILE=/etc/hyperledger/fabric/tls/server.crt
#      - CORE_PEER_TLS_KEY_FILE=/etc/hyperledger/fabric/tls/server.key
#      - CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/fabric/tls/ca.crt

    #  - CORE_PEER_GOSSIP_USELEADERELECTION=true
     # - CORE_PEER_GOSSIP_ORGLEADER=false
     # - CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org1.trace.com:7051
     # - CORE_PEER_GOSSIP_BOOTSTRAP=peer0.org1.trace.com:7051
    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
    command: peer node start
    #command: peer node start --peer-chaincodedev=true
    ports:
      - 7051:7051
#      - 7052:7052
      - 7053:7053
    volumes:
        - /var/run/:/host/var/run/
        - ./crypto-config/peerOrganizations/org1.trace.com/peers/peer0.org1.trace.com/msp:/etc/hyperledger/msp/peer
        - ./crypto-config/peerOrganizations/org1.trace.com/users:/etc/hyperledger/msp/users
        - ./config:/etc/hyperledger/configtx
#        - ./crypto-config/peerOrganizations/org1.trace.com/peers/peer0.org1.trace.com/msp:/etc/hyperledger/fabric/msp
#        - ./crypto-config/peerOrganizations/org1.trace.com/peers/peer0.org1.trace.com/tls:/etc/hyperledger/fabric/tls
        - peer0.org1.trace.com:/var/hyperledger/production
    depends_on:
      - orderer.trace.com
      - couchdb
    networks:
      - basic


  peer0.org2.trace.com:
    container_name: peer0.org2.trace.com
    image: hyperledger/fabric-peer
    environment:
      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
      - CORE_PEER_ID=peer0.org2.trace.com
      - CORE_LOGGING_PEER=info
      - CORE_CHAINCODE_LOGGING_LEVEL=info
      - CORE_PEER_LOCALMSPID=Org2MSP
      - CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/msp/peer/
      - CORE_PEER_ADDRESS=peer0.org2.trace.com:7051
      # # the following setting starts chaincode containers on the same
      # # bridge network as the peers
      # # https://docs.docker.com/compose/networking/
      - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=basic-network_basic
      - CORE_LEDGER_STATE_STATEDATABASE=CouchDB
      - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb:5984
      # The CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME and CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD
      # provide the credentials for ledger to connect to CouchDB.  The username and password must
      # match the username and password set for the associated CouchDB.
      - CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME=
      - CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD=
      # enabled TLS
#      - CORE_PEER_TLS_ENABLED=true
#      - CORE_PEER_PROFILE_ENABLED=true
#      - CORE_PEER_TLS_CERT_FILE=/etc/hyperledger/fabric/tls/server.crt
#      - CORE_PEER_TLS_KEY_FILE=/etc/hyperledger/fabric/tls/server.key
#      - CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/fabric/tls/ca.crt
      
      #- CORE_PEER_GOSSIP_USELEADERELECTION=true
      #- CORE_PEER_GOSSIP_ORGLEADER=false
      #- CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org2.trace.com:7051
      #- CORE_PEER_GOSSIP_BOOTSTRAP=peer0.org2.trace.com:7051

    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
    command: peer node start
    #command: peer node start --peer-chaincodedev=true
    ports:
      - 8051:7051
#      - 8052:7052
      - 8053:7053
    volumes:
        - /var/run/:/host/var/run/
        - ./crypto-config/peerOrganizations/org2.trace.com/peers/peer0.org2.trace.com/msp:/etc/hyperledger/msp/peer
        - ./crypto-config/peerOrganizations/org2.trace.com/users:/etc/hyperledger/msp/users
        - ./config:/etc/hyperledger/configtx
#        - ./crypto-config/peerOrganizations/org2.trace.com/peers/peer0.org2.trace.com/msp:/etc/hyperledger/fabric/msp
#        - ./crypto-config/peerOrganizations/org2.trace.com/peers/peer0.org2.trace.com/tls:/etc/hyperledger/fabric/tls
        - peer0.org2.trace.com:/var/hyperledger/production
    depends_on:
      - orderer.trace.com
      - couchdb
    networks:
      - basic


  peer0.org3.trace.com:
    container_name: peer0.org3.trace.com
    image: hyperledger/fabric-peer
    environment:
      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
      - CORE_PEER_ID=peer0.org3.trace.com
      - CORE_LOGGING_PEER=info
      - CORE_CHAINCODE_LOGGING_LEVEL=info
      - CORE_PEER_LOCALMSPID=Org3MSP
      - CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/msp/peer/
      - CORE_PEER_ADDRESS=peer0.org3.trace.com:7051
      # # the following setting starts chaincode containers on the same
      # # bridge network as the peers
      # # https://docs.docker.com/compose/networking/
      - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=basic-network_basic
      - CORE_LEDGER_STATE_STATEDATABASE=CouchDB
      - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb:5984
      # The CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME and CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD
      # provide the credentials for ledger to connect to CouchDB.  The username and password must
      # match the username and password set for the associated CouchDB.
      - CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME=
      - CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD=
      # enabled TLS
#      - CORE_PEER_TLS_ENABLED=true
#      - CORE_PEER_PROFILE_ENABLED=true
#      - CORE_PEER_TLS_CERT_FILE=/etc/hyperledger/fabric/tls/server.crt
#      - CORE_PEER_TLS_KEY_FILE=/etc/hyperledger/fabric/tls/server.key
#      - CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/fabric/tls/ca.crt

      #- CORE_PEER_GOSSIP_USELEADERELECTION=true
      #- CORE_PEER_GOSSIP_ORGLEADER=false
      #- CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org3.trace.com:7051
      #- CORE_PEER_GOSSIP_BOOTSTRAP=peer0.org3.trace.com:7051
    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
    command: peer node start
    #command: peer node start --peer-chaincodedev=true
    ports:
      - 9051:7051
      - 9053:7053
    volumes:
        - /var/run/:/host/var/run/
        - ./crypto-config/peerOrganizations/org3.trace.com/peers/peer0.org3.trace.com/msp:/etc/hyperledger/msp/peer
        - ./crypto-config/peerOrganizations/org3.trace.com/users:/etc/hyperledger/msp/users
        - ./config:/etc/hyperledger/configtx
#        - ./crypto-config/peerOrganizations/org3.trace.com/peers/peer0.org3.trace.com/msp:/etc/hyperledger/fabric/msp
#        - ./crypto-config/peerOrganizations/org3.trace.com/peers/peer0.org3.trace.com/tls:/etc/hyperledger/fabric/tls
        - peer0.org3.trace.com:/var/hyperledger/production
    depends_on:
      - orderer.trace.com
      - couchdb
    networks:
      - basic


  peer0.org4.trace.com:
    container_name: peer0.org4.trace.com
    image: hyperledger/fabric-peer
    environment:
      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
      - CORE_PEER_ID=peer0.org4.trace.com
      - CORE_LOGGING_PEER=info
      - CORE_CHAINCODE_LOGGING_LEVEL=info
      - CORE_PEER_LOCALMSPID=Org4MSP
      - CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/msp/peer/
      - CORE_PEER_ADDRESS=peer0.org4.trace.com:7051
      # # the following setting starts chaincode containers on the same
      # # bridge network as the peers
      # # https://docs.docker.com/compose/networking/
      - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=basic-network_basic
      - CORE_LEDGER_STATE_STATEDATABASE=CouchDB
      - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb:5984
      # The CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME and CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD
      # provide the credentials for ledger to connect to CouchDB.  The username and password must
      # match the username and password set for the associated CouchDB.
      - CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME=
      - CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD=
      # enabled TLS
 #     - CORE_PEER_TLS_ENABLED=true
 #     - CORE_PEER_PROFILE_ENABLED=true
 #     - CORE_PEER_TLS_CERT_FILE=/etc/hyperledger/fabric/tls/server.crt
 #     - CORE_PEER_TLS_KEY_FILE=/etc/hyperledger/fabric/tls/server.key
 #     - CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/fabric/tls/ca.crt

      #- CORE_PEER_GOSSIP_USELEADERELECTION=true
      #- CORE_PEER_GOSSIP_ORGLEADER=false
      #- CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org4.trace.com:7051
      #- CORE_PEER_GOSSIP_BOOTSTRAP=peer0.org4.trace.com:7051
    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
    command: peer node start
    #command: peer node start --peer-chaincodedev=true
    ports:
      - 10051:7051
      - 10053:7053
    volumes:
        - /var/run/:/host/var/run/
        - ./crypto-config/peerOrganizations/org4.trace.com/peers/peer0.org4.trace.com/msp:/etc/hyperledger/msp/peer
        - ./crypto-config/peerOrganizations/org4.trace.com/users:/etc/hyperledger/msp/users
        - ./config:/etc/hyperledger/configtx
 #       - ./crypto-config/peerOrganizations/org4.trace.com/peers/peer0.org4.trace.com/msp:/etc/hyperledger/fabric/msp
 #       - ./crypto-config/peerOrganizations/org4.trace.com/peers/peer0.org4.trace.com/tls:/etc/hyperledger/fabric/tls
        - peer0.org4.trace.com:/var/hyperledger/production
    depends_on:
      - orderer.trace.com
      - couchdb
    networks:
      - basic

  peer0.org5.trace.com:
    container_name: peer0.org5.trace.com
    image: hyperledger/fabric-peer
    environment:
      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
      - CORE_PEER_ID=peer0.org4.trace.com
      - CORE_LOGGING_PEER=info
      - CORE_CHAINCODE_LOGGING_LEVEL=info
      - CORE_PEER_LOCALMSPID=Org5MSP
      - CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/msp/peer/
      - CORE_PEER_ADDRESS=peer0.org5.trace.com:7051
      # # the following setting starts chaincode containers on the same
      # # bridge network as the peers
      # # https://docs.docker.com/compose/networking/
      - CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=basic-network_basic
      - CORE_LEDGER_STATE_STATEDATABASE=CouchDB
      - CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb:5984
      # The CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME and CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD
      # provide the credentials for ledger to connect to CouchDB.  The username and password must
      # match the username and password set for the associated CouchDB.
      - CORE_LEDGER_STATE_COUCHDBCONFIG_USERNAME=
      - CORE_LEDGER_STATE_COUCHDBCONFIG_PASSWORD=
      # enabled TLS
#      - CORE_PEER_TLS_ENABLED=true
#      - CORE_PEER_PROFILE_ENABLED=true
#      - CORE_PEER_TLS_CERT_FILE=/etc/hyperledger/fabric/tls/server.crt
#      - CORE_PEER_TLS_KEY_FILE=/etc/hyperledger/fabric/tls/server.key
#      - CORE_PEER_TLS_ROOTCERT_FILE=/etc/hyperledger/fabric/tls/ca.crt
 
      #- CORE_PEER_GOSSIP_USELEADERELECTION=true
      #- CORE_PEER_GOSSIP_ORGLEADER=false
      #- CORE_PEER_GOSSIP_EXTERNALENDPOINT=peer0.org5.trace.com:7051
      #- CORE_PEER_GOSSIP_BOOTSTRAP=peer0.org5.trace.com:7051
    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
    command: peer node start
    #command: peer node start --peer-chaincodedev=true
    ports:
      - 11051:7051
      - 11053:7053
    volumes:
        - /var/run/:/host/var/run/
        - ./crypto-config/peerOrganizations/org5.trace.com/peers/peer0.org5.trace.com/msp:/etc/hyperledger/msp/peer
        - ./crypto-config/peerOrganizations/org5.trace.com/users:/etc/hyperledger/msp/users
        - ./config:/etc/hyperledger/configtx
#        - ./crypto-config/peerOrganizations/org5.trace.com/peers/peer0.org5.trace.com/msp:/etc/hyperledger/fabric/msp
#        - ./crypto-config/peerOrganizations/org5.trace.com/peers/peer0.org5.trace.com/tls:/etc/hyperledger/fabric/tls
        - peer0.org5.trace.com:/var/hyperledger/production
    depends_on:
      - orderer.trace.com
      - couchdb
    networks:
      - basic


  couchdb:
    container_name: couchdb
    image: hyperledger/fabric-couchdb
    # Populate the COUCHDB_USER and COUCHDB_PASSWORD to set an admin user and password
    # for CouchDB.  This will prevent CouchDB from operating in an "Admin Party" mode.
    environment:
      - COUCHDB_USER=
      - COUCHDB_PASSWORD=
    ports:
      - 5984:5984
    networks:
      - basic

  cli:
    container_name: cli
    image: hyperledger/fabric-tools
    tty: true
    stdin_open: true
    environment:
      - GOPATH=/opt/gopath
      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
      - CORE_LOGGING_LEVEL=info
      - CORE_PEER_ID=cli
      - CORE_PEER_ADDRESS=peer0.org1.trace.com:7051
      - CORE_PEER_LOCALMSPID=Org1MSP
      - CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.trace.com/users/Admin@org1.trace.com/msp
      - CORE_CHAINCODE_KEEPALIVE=10
#      - CORE_PEER_TLS_ENABLED=true
#      - CORE_PEER_TLS_CERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.trace.com/peers/peer0.org1.trace.com/tls/server.crt
#      - CORE_PEER_TLS_KEY_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.trace.com/peers/peer0.org1.trace.com/tls/server.key
#      - CORE_PEER_TLS_ROOTCERT_FILE=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.trace.com/peers/peer0.org1.trace.com/tls/ca.crt
    working_dir: /opt/gopath/src/github.com/hyperledger/fabric/peer
    command: /bin/bash
    volumes:
        - /var/run/:/host/var/run/
        - ./../chaincode/:/opt/gopath/src/github.com/chaincode
        - ./crypto-config:/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/
        - ./scripts:/opt/gopath/src/github.com/hyperledger/fabric/peer/scripts/
        - ./channel-artifacts:/opt/gopath/src/github.com/hyperledger/fabric/peer/channel-artifacts
    depends_on:
      - orderer.trace.com
      - peer0.org1.trace.com
      - peer0.org2.trace.com
      - peer0.org3.trace.com
      - peer0.org4.trace.com
      - peer0.org5.trace.com

    networks:
        - basic
    #depends_on:
    #  - orderer.example.com
    #  - peer0.org1.example.com
    #  - couchdb

3 問題解決記錄

問題解決：

Error: error getting endorser client for channel: endorser client failed to connect to peer0.org1.trace.com:7051: failed to create new connection: connection error: desc = "transport: error while dialing: dial tcp 172.22.0.7:7051: connect: connection refused"

Error: error getting endorser client for channel: endorser client failed to connect to peer0.org1.trace.com:7051: failed to create new connection: context deadline exceeded

解決方法：

sudo vi /etc/resolv.conf

hyperledger fabric網(wǎng)絡(luò)操作基本操作和概念,深入探索hyperledger fabric聯(lián)盟鏈搭建,fabric,網(wǎng)絡(luò),區(qū)塊鏈

按:wq!退出

4 啟動(dòng)區(qū)塊鏈docker節(jié)點(diǎn)

4.1 常用docker命令

刪除所有容器

# 1.停用全部運(yùn)行中的容器:
docker stop $(docker ps -q)
# 2.刪除全部容器：
docker rm $(docker ps -aq)

刪除所有鏡像

docker rmi -f $(docker images -qa)

刪除數(shù)據(jù)卷

# 刪除數(shù)據(jù)卷:
docker volume rm $(docker volume ls -q)
# 刪除 network:
docker network rm $(docker network ls -q)

一鍵執(zhí)行

docker stop $(docker ps -q)
docker rm $(docker ps -aq)
docker volume rm $(docker volume ls -q)
./start.sh

拉取對應(yīng)版本鏡像（包含區(qū)塊鏈fabric1.4.7和1.2.0）

## 1) 基礎(chǔ)鏡像
docker pull hyperledger/fabric-peer:1.4.7
docker tag hyperledger/fabric-peer:1.4.7 hyperledger/fabric-peer:latest

docker pull hyperledger/fabric-orderer:1.4.7
docker tag hyperledger/fabric-orderer:1.4.7 hyperledger/fabric-orderer:latest

docker pull hyperledger/fabric-tools:1.4.7
docker tag hyperledger/fabric-tools:1.4.7 hyperledger/fabric-tools:latest

docker pull hyperledger/fabric-ccenv:1.4.7
docker tag hyperledger/fabric-ccenv:1.4.7 hyperledger/fabric-ccenv:latest

docker pull hyperledger/fabric-ca:1.4.7
docker tag hyperledger/fabric-ca:1.4.7 hyperledger/fabric-ca:latest

## 2) 數(shù)據(jù)庫與消息隊(duì)列鏡像
docker pull hyperledger/fabric-baseos:0.4.15
docker tag hyperledger/fabric-baseos:0.4.15 hyperledger/fabric-baseos:latest

docker pull hyperledger/fabric-couchdb:0.4.15
docker tag hyperledger/fabric-couchdb:0.4.15 hyperledger/fabric-couchdb:latest

docker pull hyperledger/fabric-kafka:0.4.15
docker tag hyperledger/fabric-kafka:0.4.15 hyperledger/fabric-kafka:latest

docker pull hyperledger/fabric-zookeeper:0.4.15 
docker tag hyperledger/fabric-zookeeper:0.4.15 hyperledger/fabric-zookeeper:latest

## 3) Java語言包鏡像(可選)
# docker pull hyperledger/fabric-javaenv:1.4.7
# docker tag hyperledger/fabric-javaenv:1.4.7 hyperledger/fabric-javaenv:latest

1.2 版本

## 1) 基礎(chǔ)鏡像
docker pull hyperledger/fabric-peer:1.2.0
docker tag hyperledger/fabric-peer:1.2.0 hyperledger/fabric-peer:latest

docker pull hyperledger/fabric-orderer:1.2.0
docker tag hyperledger/fabric-orderer:1.2.0 hyperledger/fabric-orderer:latest

docker pull hyperledger/fabric-tools:1.2.0
docker tag hyperledger/fabric-tools:1.2.0 hyperledger/fabric-tools:latest

docker pull hyperledger/fabric-ccenv:1.2.0
docker tag hyperledger/fabric-ccenv:1.2.0 hyperledger/fabric-ccenv:latest

docker pull hyperledger/fabric-ca:1.2.0
docker tag hyperledger/fabric-ca:1.2.0 hyperledger/fabric-ca:latest

## 2) 數(shù)據(jù)庫與消息隊(duì)列鏡像
docker pull hyperledger/fabric-baseos:0.4.10
docker tag hyperledger/fabric-baseos:0.4.10 hyperledger/fabric-baseos:latest

docker pull hyperledger/fabric-couchdb:0.4.10
docker tag hyperledger/fabric-couchdb:0.4.10 hyperledger/fabric-couchdb:latest

docker pull hyperledger/fabric-kafka:0.4.10
docker tag hyperledger/fabric-kafka:0.4.10 hyperledger/fabric-kafka:latest

docker pull hyperledger/fabric-zookeeper:0.4.10 
docker tag hyperledger/fabric-zookeeper:0.4.10 hyperledger/fabric-zookeeper:latest

## 3) Java語言包鏡像(可選)
# docker pull hyperledger/fabric-javaenv:1.2.0
# docker tag hyperledger/fabric-javaenv:1.2.0 hyperledger/fabric-javaenv:latest

5 fabric-node-sdk后臺(tái)搭建

nodejs 后臺(tái)搭建（在ubuntu 阿里云服務(wù)器）
安裝nvm

wget -qO- https://raw.githubusercontent.com/creationix/nvm/v0.31.1/install.sh | bash

hyperledger fabric網(wǎng)絡(luò)操作基本操作和概念,深入探索hyperledger fabric聯(lián)盟鏈搭建,fabric,網(wǎng)絡(luò),區(qū)塊鏈

執(zhí)行

source ~/.bashrc

下載node依賴

nvm install 12.13.1
rm -rf node_modules
rm -rf hfc-key-store
nvm use 12.13.1
npm install
nvm use 12.13.1
npm rebuild
npm install fabric-client
npm install fabric-ca-client
node enrollAdmin.js
node registerUser.js
npm install express
npm install body-parser
npm install influx

npm install forever -g
forever start app.js

訪問http://xxx.xxx.xxx:5984/_utils/#查看區(qū)塊鏈的couchdb
hyperledger fabric網(wǎng)絡(luò)操作基本操作和概念,深入探索hyperledger fabric聯(lián)盟鏈搭建,fabric,網(wǎng)絡(luò),區(qū)塊鏈
node sdk后臺(tái)查看

docker節(jié)點(diǎn)查看
文章來源地址http://www.zghlxwxcb.cn/news/detail-796820.html

到了這里，關(guān)于hyperledger fabric 網(wǎng)絡(luò)操作基本操作和概念的文章就介紹完了。如果您還想了解更多內(nèi)容，請?jiān)谟疑辖撬阉鱐OY模板網(wǎng)以前的文章或繼續(xù)瀏覽下面的相關(guān)文章，希望大家以后多多支持TOY模板網(wǎng)！

本文來自互聯(lián)網(wǎng)用戶投稿，該文觀點(diǎn)僅代表作者本人，不代表本站立場。本站僅提供信息存儲(chǔ)空間服務(wù)，不擁有所有權(quán)，不承擔(dān)相關(guān)法律責(zé)任。如若轉(zhuǎn)載，請注明出處：如若內(nèi)容造成侵權(quán)/違法違規(guī)/事實(shí)不符，請點(diǎn)擊違法舉報(bào)進(jìn)行投訴反饋，一經(jīng)查實(shí)，立即刪除！

分享到：

領(lǐng)支付寶紅包贊助服務(wù)器費(fèi)用

王道操作系統(tǒng)學(xué)習(xí)筆記(1)——操作系統(tǒng)基本概念
本文介紹了操作系統(tǒng)的基本概念，文章中的內(nèi)容來自B站王道考研操作系統(tǒng)課程，想要完整學(xué)習(xí)的可以到B站官方看完整版。操作系統(tǒng)：系統(tǒng)資源的管理者（處理機(jī)管理、存儲(chǔ)器管理、文件管理、設(shè)備管理）交互式命令（在終端中輸命令）和批處理命令（Shell腳本）并發(fā)：宏
2024年02月10日
瀏覽(25)
棧的概念及其基本操作--詳細(xì)（C++）
基本概念及相關(guān)術(shù)語：棧是只允許在一端進(jìn)行插入和刪除操作的線性表。由此可見，棧也是線性表的一種，只是棧的操作受限制的線性表。棧頂（top）：線性表允許插入和刪除的那一段。值得注意的是，棧頂指針top的指向是有些兩種方式的，一種是指向棧頂當(dāng)前元素，
2024年02月08日
瀏覽(28)
【數(shù)據(jù)結(jié)構(gòu)】_7.二叉樹概念與基本操作
目錄 1.樹形結(jié)構(gòu) 1.1 樹的概念 1.2 樹的相關(guān)概念 1.3 樹的表示 1.4 樹在實(shí)際中的應(yīng)用—表示文件系統(tǒng)的目錄樹結(jié)構(gòu) ?編輯?2.二叉樹 2.1 概念 2.2 特殊二叉樹 ?2.3 二叉樹的性質(zhì) 2.4 二叉樹的存儲(chǔ)結(jié)構(gòu) 2.4.1 順序存儲(chǔ)結(jié)構(gòu)（數(shù)組存儲(chǔ)結(jié)構(gòu)） 2.4.2 鏈?zhǔn)酱鎯?chǔ)結(jié)構(gòu) 2.5 二叉樹的基本操作 2
2024年02月12日
瀏覽(62)
【linux】docker基本概念和基礎(chǔ)指令操作(鏡像、容器)
docker 鏡像 images xxxx(名稱):xxxx(版本號(hào)) 每一個(gè)image可以生成若干個(gè) 容器（container），所有用相同鏡像生成的容器環(huán)境完全一樣每一個(gè)容器都是一個(gè)完全獨(dú)立的云端服務(wù)器
2024年02月01日
瀏覽(54)
Docker - 基本概念、與虛擬機(jī)的區(qū)別、架構(gòu)、鏡像操作、容器操作、數(shù)據(jù)卷掛載
目錄一、對 Docker? 的理解 1、Docker 基本概念 2、Docker 與虛擬機(jī)的區(qū)別 3、何為鏡像和容器？ 4、Docker 主要架構(gòu) 二、Docker 基本操作 1、Docker 鏡像操作 2、案例（鏡像）：去 DockerHub 搜索并拉取一個(gè) Nginx 鏡像，打包后刪除鏡像，重新加載 .tar 文件 3、Docker 容器操作 1.docker run（啟
2024年04月13日
瀏覽(26)
Git 分布式版本控制系統(tǒng)基本概念和操作命令
目錄 Git 基本概念功能特點(diǎn) 工作流程操作命令新建代碼庫配置增刪文件代碼提交分支標(biāo)簽查看信息遠(yuǎn)程同步撤銷其他小結(jié) Git 是一個(gè)開源的分布式版本控制系統(tǒng)，用于跟蹤文件的變更歷史。它最初由 Linux Torvalds 設(shè)計(jì)，用于 Linux 內(nèi)核的開發(fā)，但由于其強(qiáng)大的功能和靈
2024年03月27日
瀏覽(55)
MySQL數(shù)據(jù)庫概念、管理以及SQL語句的基本命令操作
數(shù)據(jù)（data）描述事物的符號(hào)記錄包括數(shù)字，文字、圖形、圖像、聲音、檔案記錄等以“記錄”形式按統(tǒng)一格式進(jìn)行存儲(chǔ)（記錄可以看成一條記錄）表將不同的記錄組織在一起用來存儲(chǔ)具體數(shù)據(jù) 記錄：行字段（屬性）：列以行+列的形式就組成了表（數(shù)據(jù)存儲(chǔ)在表中）數(shù)
2024年02月08日
瀏覽(34)
K8S初級(jí)入門系列之三-Pod的基本概念和操作
? ? ? ?Pod的原意是豌豆莢的意思，一個(gè)豆莢里面包含了很多豆子。在K8S中，Pod也是類似的意思，只不過這里的豆子就是容器。在K8S初級(jí)入門系列之一-概述中，我們對Pod有個(gè)初步的了解。 1、Pod是K8S編排和調(diào)度的最小基礎(chǔ)單元。 ? ? ? ? 了解容器的同學(xué)會(huì)知道，容器之間通過
2024年02月15日
瀏覽(26)
Hyperledger Fabric網(wǎng)絡(luò)快速啟動(dòng)
目錄 1、網(wǎng)絡(luò)服務(wù)配置 2、關(guān)聯(lián)的docker-compose-base.yaml 各Peer節(jié)點(diǎn)容器設(shè)置如下信息。 3、被關(guān)聯(lián)的Peer-base.yaml 4、啟動(dòng)網(wǎng)絡(luò) 2、完成通道的創(chuàng)建 2.1將節(jié)點(diǎn)加入應(yīng)用通道 ?更新錨節(jié)點(diǎn) ?2.為什么要?jiǎng)?chuàng)建節(jié)點(diǎn)并將其加入應(yīng)用通道中？ ????????由于要啟動(dòng)多個(gè)網(wǎng)絡(luò)節(jié)點(diǎn)，Hyperledger Fa
2024年02月12日
瀏覽(21)
Git企業(yè)開發(fā)控制理論和實(shí)操-從入門到深入（二）｜Git的基本操作
那么這里博主先安利一些干貨滿滿的專欄了！首先是博主的高質(zhì)量博客的匯總，這個(gè)專欄里面的博客，都是博主最最用心寫的一部分，干貨滿滿，希望對大家有幫助。高質(zhì)量博客匯總 https://blog.csdn.net/yu_cblog/category_12379430.html 然后就是博主最近最花信息的一個(gè)專欄《Git企業(yè)開
2024年02月11日
瀏覽(51)

^{<track id="nzhyq"></track>}

<track id="nzhyq"><ruby id="nzhyq"></ruby></track>

<track id="nzhyq"></track>