Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhance multiparty documentation #1475

Open
EnriqueL8 opened this issue Feb 26, 2024 · 2 comments
Open

Enhance multiparty documentation #1475

EnriqueL8 opened this issue Feb 26, 2024 · 2 comments

Comments

@EnriqueL8
Copy link
Contributor

Both @SamMayWork and @Chengxuan raised in the last community call that setting up a multiparty setup using the Firefly CLI or standalone can be complicated and frustrating. Sam has gone through this process recently.

Due to this friction, we agreed on the call to enhance the documentation to help users setup a multiparty network. There are number of discord threads that could be used as a guideline of what we want to cover in the documentation:

And I think a general tutorial on how to set it up

@icemagno
Copy link

icemagno commented Mar 16, 2024

I've been waiting for this for centuries. I've been trying to configure my network for 3 months with the following objectives:

  1. Create two organizations on separate servers, but sharing an existing and 100% functional Besu blockchain, as well as an existing and functional IPFS network.

  2. Configure Data Exchange for this scenario.

  3. After having this functional environment, create another organization/node on a third server and have it join the already created environment, gaining knowledge to replicate the process as many times as necessary.

I'm stuck now in how to create a new organization, since I already done with Besu and IPFS. I don't know how to make another Org/Node because the DataExchange key and cert and the /api/v1/network/organizations POST endpoint is very poor in examples in what I need to do before call it ( who will handle the dataexchange certificates distribution ? me ? )

So.. Need I to take the new certificate and put it in all dataexchange cert-peers folder and restart them all?

How to deal with peering?

@EnriqueL8 Many many thanks to give a light on this question.

@EnriqueL8
Copy link
Contributor Author

Yes, definitely a lot of content that is missing and now should be easier to automate and configure with the Helm Chart https://github.com/hyperledger/firefly-helm-charts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants