With version 3.0, you introduced the "networkId" as a parameter to many flows, letting us believe we can handle multiple networks. But something is still unclear to me:
How many membership-service.conf files should we have? In my opinion, if we want to enable multiple networks, we should be able to have multiple configuration files, one for each network.
However, this doesn't seem to be the case, especially when I read the README in membership-management/.
So either the doc still hasn't been fully updated, or I am missing something. Can you please shed some light on my dilemma? Thank you in advance.
With version 3.0, you introduced the "networkId" as a parameter to many flows, letting us believe we can handle multiple networks. But something is still unclear to me:
How many
membership-service.conf
files should we have? In my opinion, if we want to enable multiple networks, we should be able to have multiple configuration files, one for each network.However, this doesn't seem to be the case, especially when I read the README in membership-management/.
So either the doc still hasn't been fully updated, or I am missing something. Can you please shed some light on my dilemma? Thank you in advance.