We currently have a generic make target that pulls in the latest protobuf dependencies - documented here. To prevent competing updates to our auto-generated code we should be more explicit. I quite like the documentation here

When I run make setup-master,setup-worker and make run.

How to proceed like docs

Documentation is out of date.
I cannot properly set up fabric-starter. Some things is not clear and it leads to difficult project set up.

Is your feature request related to a problem? Please describe.
Cicero server only supports a single version of the cicero trigger call through the /trigger endpoint. It might be interesting to extend the cicero server API to the rest of the commands (e.g., draft invoke parse).

Other improvements could include the ability to pass or create the template from a string (binary encode

Following instructions here, but where do we specify channelList?
No channel information defined in example on main page, you should include the full sample instead.

var config=require('../config.json')
var channels=config.channelsList

`blockchain/fabric-explorer/utils/ledgerMgr.js:23
var currChannel=channels[0]
^

TypeError: Cannot read property '0' of undefin

In the fabric tutorials that use docker and fabric sdk, there is a connection-profile file that tells the web application how to connect to the network, it contains info like endpoints of the peer containers, where to find the certificates, etc.

Is there an equivalent of the connection profile in this kubernetes based setup?