zoukankan      html  css  js  c++  java
  • HyperLedger/Fabric区块连网络-双主机,双peer,分布式fabric环境搭建

    功能是构建一个Fabric网络,其特点为,一个Orderer,一个Org(peer0peer1)

    主机A上运行orderer、ca、peer0,couchDB、cli

    主机B上运行peer1、couchDB、cli

    1. 前期准备

    主机A(Peer0)

    修改/etc/hosts,添加orderer和peer1节点的映射

    主机B(Peer1)

    2. 修改配置

    目录:/root/go/src/github.com/hyperledger/fabric-samples/basic-network

    所有配置文件都在该目录下

    2.1 修改 crypto-config.yaml

    需要几个peer就改为几。原来是1

    本生成配置文件

    ./generate.sh

    运行后会生成两个文件夹config、crypto-config

    将config、crypto-config复制到主机A、B

    2.2 修改docker-compose.yml

    主机A(peer0)

    1.修改FABRIC_CA_SERVER_CA_KEYFILE

    FABRIC_CA_SERVER_CA_KEYFILE变量中,xxx_sk文件名要和新生成下的文件链接一致,否则CA容器会启动失败.

    我们修改为:

          - FABRIC_CA_SERVER_CA_KEYFILE=/root/go/src/github.com/hyperledger/fabric-samples/basic-network/crypto-config/peerOrganizations/org1.example.com/ca/8cc66f94a3ff897e1d2d39193685a4281b353735b3deee526902a40786aea4e0_sk

    2.加hosts文件映射

    添加:

    - /etc/hosts:/etc/hosts

    注释:# - orderer.example.com

    3.cli中添加对peer0节点的依赖

    cli 部分添加:

    - peer0.org1.example.com

    docker-compose.yml

    #
    # Copyright IBM Corp All Rights Reserved
    #
    # SPDX-License-Identifier: Apache-2.0
    #
    version: '2'
    
    networks:
      basic:
    
    services:
      ca.example.com:
        image: hyperledger/fabric-ca
        environment:
          - FABRIC_CA_HOME=/etc/hyperledger/fabric-ca-server
          - FABRIC_CA_SERVER_CA_NAME=ca.example.com
          - FABRIC_CA_SERVER_CA_CERTFILE=/etc/hyperledger/fabric-ca-server-config/ca.org1.example.com-cert.pem
        #  - FABRIC_CA_SERVER_CA_KEYFILE=/etc/hyperledger/fabric-ca-server-config/4239aa0dcd76daeeb8ba0cda701851d14504d31aad1b2ddddbac6a57365e497c_sk
          - FABRIC_CA_SERVER_CA_KEYFILE=/root/go/src/github.com/hyperledger/fabric-samples/basic-network/crypto-config/peerOrganizations/org1.example.com/ca/8cc66f94a3ff897e1d2d39193685a4281b353735b3deee526902a40786aea4e0_sk
        ports:
          - "7054:7054"
        command: sh -c 'fabric-ca-server start -b admin:adminpw -d'
        volumes:
          - ./crypto-config/peerOrganizations/org1.example.com/ca/:/etc/hyperledger/fabric-ca-server-config
        container_name: ca.example.com
        networks:
          - basic
    
      orderer.example.com:
        container_name: orderer.example.com
        image: hyperledger/fabric-orderer
        environment:
          - ORDERER_GENERAL_LOGLEVEL=debug
          - ORDERER_GENERAL_LISTENADDRESS=0.0.0.0
          - ORDERER_GENERAL_GENESISMETHOD=file
          - ORDERER_GENERAL_GENESISFILE=/etc/hyperledger/configtx/genesis.block
          - ORDERER_GENERAL_LOCALMSPID=OrdererMSP
          - ORDERER_GENERAL_LOCALMSPDIR=/etc/hyperledger/msp/orderer/msp
        working_dir: /opt/gopath/src/github.com/hyperledger/fabric/orderer
        command: orderer
        ports:
          - 7050:7050
        volumes:
            - ./config/:/etc/hyperledger/configtx
            - ./crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/:/etc/hyperledger/msp/orderer
            - ./crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/:/etc/hyperledger/msp/peerOrg1
        networks:
          - basic
    
      peer0.org1.example.com:
        container_name: peer0.org1.example.com
        image: hyperledger/fabric-peer
        environment:
          - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
          - CORE_PEER_ID=peer0.org1.example.com
          - CORE_LOGGING_PEER=debug
          - CORE_CHAINCODE_LOGGING_LEVEL=DEBUG
          - CORE_PEER_LOCALMSPID=Org1MSP
          - CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/msp/peer/
          - CORE_PEER_ADDRESS=peer0.org1.example.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=${COMPOSE_PROJECT_NAME}_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=
        working_dir: /opt/gopath/src/github.com/hyperledger/fabric
        command: peer node start
        # command: peer node start --peer-chaincodedev=true
        ports:
          - 7051:7051
          - 7053:7053
        volumes:
            - /var/run/:/host/var/run/
            - ./crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/msp:/etc/hyperledger/msp/peer
            - ./crypto-config/peerOrganizations/org1.example.com/users:/etc/hyperledger/msp/users
            - ./config:/etc/hyperledger/configtx
            - /etc/hosts:/etc/hosts  #add hosts
        depends_on:
         # - orderer.example.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
        environment:
          - GOPATH=/opt/gopath
          - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
          - CORE_LOGGING_LEVEL=DEBUG
          - CORE_PEER_ID=cli
          - CORE_PEER_ADDRESS=peer0.org1.example.com:7051
          - CORE_PEER_LOCALMSPID=Org1MSP
          - CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
          - CORE_CHAINCODE_KEEPALIVE=10
        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/
            - ./crypto-config:/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/
        networks:
            - basic
        depends_on:
        #  - orderer.example.com
           - peer0.org1.example.com
        #  - couchdb

    主机B(peer1)

    复制原始的docker-compose.yml文件,粘贴为docker-compose2.yml去除ordererca服务配置,并对peercli做修改

    1.peer配置修改

    修改节点名称为peer0为peer1
    volumes里添加hosts映射
    依赖中去除orderer相关配置

    2.cli配置修改


    修改peer0为peer1
    添加peer1节点依赖

    #
    # Copyright IBM Corp All Rights Reserved
    #
    # SPDX-License-Identifier: Apache-2.0
    #
    version: '2'
    
    networks:
      basic:
    
    services:
    
      peer1.org1.example.com:
        container_name: peer1.org1.example.com
        image: hyperledger/fabric-peer
        environment:
          - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
          - CORE_PEER_ID=peer1.org1.example.com
          - CORE_LOGGING_PEER=debug
          - CORE_CHAINCODE_LOGGING_LEVEL=DEBUG
          - CORE_PEER_LOCALMSPID=Org1MSP
          - CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/msp/peer/
          - CORE_PEER_ADDRESS=peer1.org1.example.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=${COMPOSE_PROJECT_NAME}_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=
        working_dir: /opt/gopath/src/github.com/hyperledger/fabric
        command: peer node start
        # command: peer node start --peer-chaincodedev=true
        ports:
          - 7051:7051
          - 7053:7053
        volumes:
            - /var/run/:/host/var/run/
            - ./crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/msp:/etc/hyperledger/msp/peer
            - ./crypto-config/peerOrganizations/org1.example.com/users:/etc/hyperledger/msp/users
            - ./config:/etc/hyperledger/configtx
            - /etc/hosts:/etc/hosts  #add hosts
        depends_on:
         # - orderer.example.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
        environment:
          - GOPATH=/opt/gopath
          - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock
          - CORE_LOGGING_LEVEL=DEBUG
          - CORE_PEER_ID=cli
          - CORE_PEER_ADDRESS=peer1.org1.example.com:7051
          - CORE_PEER_LOCALMSPID=Org1MSP
          - CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp
          - CORE_CHAINCODE_KEEPALIVE=10
        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/
            - ./crypto-config:/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/
        networks:
            - basic
        depends_on:
        #  - orderer.example.com
           - peer1.org1.example.com
        #  - couchdb

    2.3 修改脚本

    主机Apeer0

    修改start.sh脚本,添加从容器中将信道文件导出到/tmp/目录下

    #!/bin/bash
    #
    # Copyright IBM Corp All Rights Reserved
    #
    # SPDX-License-Identifier: Apache-2.0
    #
    # Exit on first error, print all commands.
    set -ev
    
    # don't rewrite paths for Windows Git Bash users
    export MSYS_NO_PATHCONV=1
    
    docker-compose -f docker-compose.yml down
    
    docker-compose -f docker-compose.yml up -d ca.example.com orderer.example.com peer0.org1.example.com couchdb
    
    # wait for Hyperledger Fabric to start
    # incase of errors when running later commands, issue export FABRIC_START_TIMEOUT=<larger number>
    export FABRIC_START_TIMEOUT=10
    #echo ${FABRIC_START_TIMEOUT}
    sleep ${FABRIC_START_TIMEOUT}
    
    # Create the channel
    docker exec -e "CORE_PEER_LOCALMSPID=Org1MSP" -e "CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/msp/users/Admin@org1.example.com/msp" peer0.org1.example.com peer channel create -o orderer.example.com:7050 -c mychannel -f /etc/hyperledger/configtx/channel.tx
    
    #copy mychannl.tx
    docker cp peer0.org1.example.com:/opt/gopath/src/github.com/hyperledger/fabric/mychannel.block /tmp/
    
    # Join peer0.org1.example.com to the channel.
    docker exec -e "CORE_PEER_LOCALMSPID=Org1MSP" -e "CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/msp/users/Admin@org1.example.com/msp" peer0.org1.example.com peer channel join -b mychannel.block

    主机Bpeer1

    复制原始的start.sh文件,粘贴为start2.sh文件,清空内容并写入如下:

    #!/bin/bash
    #
    # Copyright IBM Corp All Rights Reserved
    #
    # SPDX-License-Identifier: Apache-2.0
    #
    # Exit on first error, print all commands.
    set -ev
    
    # don't rewrite paths for Windows Git Bash users
    export MSYS_NO_PATHCONV=1
    
    docker-compose -f docker-compose2.yml down
    
    docker-compose -f docker-compose2.yml up -d peer1.org1.example.com couchdb
    
    # wait for Hyperledger Fabric to start
    # incase of errors when running later commands, issue export FABRIC_START_TIMEOUT=<larger number>
    export FABRIC_START_TIMEOUT=10
    #echo ${FABRIC_START_TIMEOUT}
    sleep ${FABRIC_START_TIMEOUT}
    
    
    #cp channel
    docker cp /tmp/mychannel.block peer1.org1.example.com:/opt/gopath/src/github.com/hyperledger/fabric/
    
    # Join peer1.org1.example.com to the channel.
    docker exec -e "CORE_PEER_LOCALMSPID=Org1MSP" -e "CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/msp/users/Admin@org1.example.com/msp" peer1.org1.example.com peer channel join -b mychannel.block

    3. 启动网络

    3.1 主机Apeer0

    创建脚本startp3.sh

    fabcar目录下,新建startp3.sh脚本,

     

    特别注意这个参数  CC_SRC_PATH=github.com/fabcar

    这个是登录容器以后相对chaincode的目录位置

    如果运行报错的话不着急退出,登录容器客户端docker exec -it cli bash

    然后查看chaincode的具体位置,然后修改。

    root@ubuntu:~/go/src/github.com/hyperledger/fabric-samples/basic-network# cat startp3.sh 
    #!/bin/bash
    #
    # 没有链码实例化,用于多机分布运行
    # Exit on first error
    set -e
    
    # don't rewrite paths for Windows Git Bash users
    export MSYS_NO_PATHCONV=1
    starttime=$(date +%s)
    LANGUAGE=${1:-"golang"}
    CC_SRC_PATH=github.com/fabcar
    #CC_SRC_PATH=/root/go/src/github.com/hyperledger/fabric/examples/e2e_cli/examples/chaincode/go/chaincode_example02
    if [ "$LANGUAGE" = "node" -o "$LANGUAGE" = "NODE" ]; then
        CC_SRC_PATH=/opt/gopath/src/github.com/fabcar/node
    fi
    
    # clean the keystore
    # rm -rf ./hfc-key-store
    
    # launch network; copy channel and join peer to channel
    cd ../basic-network
    ./start.sh
    
    # Now launch the CLI container in order to install, instantiate chaincode
    docker-compose -f ./docker-compose.yml up -d cli
    
    docker exec -e "CORE_PEER_LOCALMSPID=Org1MSP" -e "CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp" cli peer chaincode install -n fabcar -v 1.0 -p "$CC_SRC_PATH" -l "$LANGUAGE"
    
    #sleep 10
    printf "
    Total setup execution time : $(($(date +%s) - starttime)) secs ...
    
    
    "
    启动脚本

     ./startp3.sh

    输出内容:

     

     复制mychannel.block 文件

    复制的/tmp/信道文件发送到主机B/tmp/目录下,

    注意:重新部署的时候会被清空,所以每次部署都需要进行该操作。

    3.2 主机Bpeer1

    创建脚本startp4.sh

     

    同样注意配置:CC_SRC_PATH=github.com/fabcar

    #!/bin/bash
    #
    # 没有链码实例化,用于多机分布运行
    # Exit on first error
    set -e
    
    # don't rewrite paths for Windows Git Bash users
    export MSYS_NO_PATHCONV=1
    starttime=$(date +%s)
    LANGUAGE=${1:-"golang"}
    CC_SRC_PATH=github.com/fabcar
    if [ "$LANGUAGE" = "node" -o "$LANGUAGE" = "NODE" ]; then
            CC_SRC_PATH=/opt/gopath/src/github.com/fabcar/node
    fi
    
    # clean the keystore
    # rm -rf ./hfc-key-store
    
    # launch network; copy channel and join peer to channel
    cd ../basic-network
    ./start2.sh
    
    # Now launch the CLI container in order to install, instantiate chaincode
    docker-compose -f ./docker-compose2.yml up -d cli
    
    docker exec -e "CORE_PEER_LOCALMSPID=Org1MSP" -e "CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp" cli peer chaincode install -n fabcar -v 1.0 -p "$CC_SRC_PATH" -l "$LANGUAGE"
    # 链码实例化是针对信道
    
    #sleep 10
    printf "
    Total setup execution time : $(($(date +%s) - starttime)) secs ...
    
    
    "
    启动脚本

    输出信息

     

    3.3 实例化链玛容器

     链玛只需实例化一次

     

    1.主机A(peer0) 上进行实例化

    docker exec -e "CORE_PEER_LOCALMSPID=Org1MSP" -e "CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp" cli peer chaincode instantiate -o orderer.example.com:7050 -C mychannel -n fabcar -l "golang" -v 1.0 -c '{"Args":[""]}' -P "OR ('Org1MSP.member','Org2MSP.member')"

    执行后发现出现了实例化后的链玛容器

    查看B主机容器,发现未出现链玛容器,

    网友说:不必担心,后面使用peer1进行交互时会自动构造链玛容器

    4. 测试(不知道是不是本地是虚拟机的原因,测试没有成功,)

    在主机Bpeer1)上执行invoke操作,主机Apeer0)上查询结果

     

    1.peer1上执行invoke put A 9

    docker exec -e "CORE_PEER_LOCALMSPID=Org1MSP" -e "CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp" cli peer chaincode invoke -o orderer.example.com:7050 -C mychannel -n fabcar -c '{"function":"put","Args":["A","9"]}'

    2.peer0上执行query A

    docker exec -e "CORE_PEER_LOCALMSPID=Org1MSP" -e "CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp" cli peer chaincode query  -C mychannel -n fabcar -c '{"function":"get","Args":["A"]}'

    参考资料:https://www.jianshu.com/p/23ab88f6723d

    ## Copyright IBM Corp All Rights Reserved## SPDX-License-Identifier: Apache-2.0#version: '2'
    networks:  basic:
    services:
      peer1.org1.example.com:    container_name: peer1.org1.example.com    image: hyperledger/fabric-peer    environment:      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock      - CORE_PEER_ID=peer1.org1.example.com      - CORE_LOGGING_PEER=debug      - CORE_CHAINCODE_LOGGING_LEVEL=DEBUG      - CORE_PEER_LOCALMSPID=Org1MSP      - CORE_PEER_MSPCONFIGPATH=/etc/hyperledger/msp/peer/      - CORE_PEER_ADDRESS=peer1.org1.example.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=${COMPOSE_PROJECT_NAME}_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=    working_dir: /opt/gopath/src/github.com/hyperledger/fabric    command: peer node start    # command: peer node start --peer-chaincodedev=true    ports:      - 7051:7051      - 7053:7053    volumes:        - /var/run/:/host/var/run/        - ./crypto-config/peerOrganizations/org1.example.com/peers/peer0.org1.example.com/msp:/etc/hyperledger/msp/peer        - ./crypto-config/peerOrganizations/org1.example.com/users:/etc/hyperledger/msp/users        - ./config:/etc/hyperledger/configtx        - /etc/hosts:/etc/hosts  #add hosts    depends_on:     # - orderer.example.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    environment:      - GOPATH=/opt/gopath      - CORE_VM_ENDPOINT=unix:///host/var/run/docker.sock      - CORE_LOGGING_LEVEL=DEBUG      - CORE_PEER_ID=cli      - CORE_PEER_ADDRESS=peer1.org1.example.com:7051      - CORE_PEER_LOCALMSPID=Org1MSP      - CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp      - CORE_CHAINCODE_KEEPALIVE=10    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/        - ./crypto-config:/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/    networks:        - basic    depends_on:    #  - orderer.example.com       - peer1.org1.example.com    #  - couchdb

  • 相关阅读:
    开发时需要安装的插件
    update svn cache 慢
    eclipse cut copy paste plugin
    eclipse怎么自定义工具栏
    Eclipse Class Decompiler——Java反编译插件(转)
    2014年下半年软考系统架构设计师考试试题
    IT痴汉的工作现状36-做好准备再上路
    JSP简单练习-EL获取表单数据
    !HDU 1078 FatMouse and Cheese-dp-(记忆化搜索)
    iOS百度地图
  • 原文地址:https://www.cnblogs.com/adao21/p/13565120.html
Copyright © 2011-2022 走看看