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.

Sign up for GitHub

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

Update .gitignore: ignoring .idea path #937

Merged
merged 2 commits into from
Aug 8, 2022
Merged

Update .gitignore: ignoring .idea path #937

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6c656b5
Update .gitignore: ignoring .idea path
kmilodenisglez Aug 6, 2022
7e5bd21
Updates to fabric_remote tutorial
kmilodenisglez Aug 6, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,3 +16,4 @@ __debug*
!deploy/charts/firefly
containerlogs
.vscode/*.log
.idea
8 changes: 4 additions & 4 deletions docs/tutorials/fabric_remote.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ Choose a stack name. For this guide, I will choose the name `my-remote-fabric`,
stack name: my-remote-fabric
```

For this guide, we will be creating only one supernode for one of the organizations in our fabric netwok and using that organizational identity to interact with the chaincode. You can create multiple supernodes for different organizations in your fabric network by passing here the number of members in your stack.
For this guide, we will be creating only one supernode for one of the organizations in our fabric network and using that organizational identity to interact with the chaincode. You can create multiple supernodes for different organizations in your fabric network by passing here the number of members in your stack.

```
number of members: 1
Expand Down Expand Up @@ -64,11 +64,11 @@ Now that you have created a stack, let's open it up in your favourite code edito

### Add msp folder representing your fabric identity

In `$HOME/.firefly/stacks/my-remote-fabric`, you need to add an msp folder. This msp folder essentially describes the fabric organizational identiy which will be interacting with your chaincode. Inside the msp folder, you must have all the certifactes and the private key to be used by firefly to query/invoke your chaincode.
In `$HOME/.firefly/stacks/my-remote-fabric`, you need to add a msp folder. This msp folder essentially describes the fabric organizational identity which will be interacting with your chaincode. Inside the msp folder, you must have all the certificates and the private key to be used by firefly to query/invoke your chaincode.

You should be having this msp folder for an organizational identity from when you would have set up your fabric network. For more details, please refer to [Hyperledger Fabric Documentation for MSP](https://hyperledger-fabric.readthedocs.io/en/latest/msp.html).

Now, you need to mount this msp directory as a docker volume in your fabconnect serivce.
Now, you need to mount this msp directory as a docker volume in your fabconnect service.

> **NOTE:** All docker-compose.yml related changes should be done in docker-compose.override.yml.

Expand Down Expand Up @@ -228,7 +228,7 @@ ff start my-remote-fabric

This may take a minute or two and in the background the FireFly CLI will do the following for you:

- Download Docker images for all of the components of the Supernode
- Download Docker images for all the components of the Supernode
- Set up configuration between all the components
- Deploy FireFly's `BatchPin` smart contract to our remote fabric network
- Register an identity for each member and node in our remote fabric network
Expand Down