Really need some hard copy of these commands for cut-n-paste.

After three lessons in this Course, totaling about 27 minutes, I can say that it’s well explained and every command line has worked perfectly.  However, I can also say: “you’ve got to be kidding!”  Is this the only/best way to manage HL-Fabric in a test environment?  Compared to the testing methodology in your Ethereum Courses, this is way too complex and time-consuming.  The only thing that would have helped would be to have had all those individual command lines available for some kind of cut-n-paste.

And that still begs the questions: “Are there no tools for managing these HL config updates?”  “Is Docker the only way?”  “How often are these types of updates going be needed in testing?”

I like the permissioned channels and other features of HL, but my experience so far with managing a test bed is a real put-off.  You must have expended an enormous amount of time getting that litany of cli commands just right … and I can’t imagine putting that much effort into getting every config update I might need into testing.  What do you guys see in terms of better HL management tools coming down the road?

Best answer

Niloo Ravaei
Niloo Ravaei
Having said that – I have added the commands for each lesson to the commands section – so hopefully that helps!


  1. 2
    Niloo Ravaei
    Niloo Ravaei
    Hi Ben, 

    Definitely understand some of your frustration here – the commands are long. 

    However, as I mentioned in a video, you will never have to do any of this in real life. You won’t need docker, and you won’t need to set and switch environment variables. Your will get your identity materials and set those variables once, and the only commands you will need are the peer commands for invoking and interacting with chaincode from your own machine. 

    We are creating a simulation of a network – even when you’re building projects and testing, you will not be switching back and forth between multiple environments the way we did in these videos. 

    The reason I structured the videos this way is to give students a sense of how the private network operates and how to add a new organization to a network, which wouldn’t be possible without having a simulated network. 

    Another point to note is that the lessons in HL201 are meant for system administrators, not developers. In the enterprise setting, system administrators deal with setting up networks / adding organizations etc. all the time, so these tasks are not too far from what they’re used to. The Etheruem testing and development, on the other hand are meant for developers, so they are made in a way that caters to their needs. 

    Once we get into our Chaincode for Developers section in our next Hyperledger Course, you will see more similarities between Hyperledger and Ethereum. 

    We do need to share these lessons on system administration however, because that is a big part of maintaining a Hyperledger network. For Etheruem, that network is public and upgraded / maintained by Ethereum core developers.