Composer-Version: v0.19.12
NPM-Version: 6.1.0
Clone the repo.
Go to /src/config.js
Run your local BCDB Instance
Check if it has data ./test.bcdb.py
Populate it with data if it is empty node populate_bcdb.js !!!! NOT PYTHON SCRIPT ANYMORE !!!!
Run your IPFS Daemon(Not Required if src/config.js dev_mode: true,)
npm install
To install and start the network for Hyperledger code:
-
Create .bna file :
composer archive create -t dir -n allianz-network -
Create PeerAdmin card (give the location of connection.json, cert and private key files to following command) :
composer card create -p connection.json -u PeerAdmin -c [email protected] -k 114aab0e76bf0c78308f89efc4b8c9423e31568da0c340ca187a9b17aa9a4457_sk -r PeerAdmin -r ChannelAdmin -
Import PeerAdmin card :
composer card import -f [email protected] -
Install network with previously created bna (version of .bna is important) :
composer network install -c PeerAdmin@allianz-network -a [email protected] -
Start the network :
composer network start --networkName allianz-network --networkVersion 0.0.36 -A admin -S adminpw -c PeerAdmin@allianz-network -
To start rest server ("never use namespace" and "no" to every option): composer-rest-server go to
localhost:3000/explorer -
To start the project: npm start in another terminal go to
localhost:30001/ics -
We have already 7 different claims in IPFS Network. You don't need to upload a file/insert something to IPFS before testing.
-
If you cannot see any claims while testing, please look at
Populate and Test Big Chain DatabaseorAfter creating bills , I cannot see any claim, What should I do?section. -
To be able to run an ipfs daemon, you should install it first. Please look at
Install IPFSsection. -
To avoid any inconsistency problem, WAIT AFTER CREATING A BILL for 3 seconds before clicking any other tab.
You need to add some dummy users to hyperledger blockchain and then create participants from them, to use login/logout functionality.
After STARTING network, use composer-playground command to start playground.
- Connect with
admin@allianz-network - Switch to test tab
http://localhost:8080/test - Create new OEs, you can use example files at
usersandoes/frenchoe.jsonandusersandoes/frenchoe.json - Create new Users, and do not forget to give reference of related Oes. you can use example files at
usersandoes/germanuser.jsonandusersandoses/frenchuser.json - Click on
adminstring that top of right-top of page, then click onID Registry - Click on
Issue new Id, write German asId nameand selectDE1as participant. Click Create-New and add it to your wallet. - Click on
Issue new Id, write French asId nameand selectFR1as participant. Click Create-New and add it to your wallet.
Now you can login with using German or French as username and their identity ids as password from localhost:30001/ics/login page.
You can find identity ids from http://localhost:3000/explorer/#!/System/System_getAllIdentities
When npm start the Allianz project first opens login page and you should enter the name of the User Participant e.g: German if you used
usersandoes/germanuser.json and session cookie can be used in any other page by getting it using req.session.user in each controller javascript. e.g:claimController it prints user details. For testing you can use cookie manager add-on for browser and can
delete the cookie and see if redirects or not. Also, you can use logout button on the top bar where user icon sits.
git clone https://github.com/bigchaindb/bigchaindb
cd bigchaindb
make run
! If you are running a mongodb instance locally, bigchaindb cannot get started. You can stop your local mongodb instance with: sudo service stop mongodb stop
If you cannot see any claims in /claims page then please follow these instructions:
In this repo, there is one python script for testing, and one javascript file for populating
To use them first install bigchaindb-driver for python3
pip3 install -U bigchaindb-driver
or if you want to use python2.x
pip install -U bigchaindb-driver
First run node populate_bcdb.js and populate your bigchaindb, and then run test_bcdp.py to retrieve results
To be able to run ipfs daemon that required for testing. First you must install ipfs to your system. Please follow these steps to install it:
- Download IPFS according to your architecture/OS from
cd go-ipfs && ./install.shipfs init- Look at your terminal and copy && paste the command that ipfs gave to you
- Start Deamon with
ipfs daemon
To be able to add file to IPFS, first install IPFS and then follow these instructions:
- Go to Allianz root then
cd ipfs npm install && npm start(Wait until its started)- Start Daemon with
ipfs daemon npm install && npm start- Go to your web browser(http://localhost:3000), add your file
If you are runninghyperldedger-playground, then you have to first close it, since they are using same ports.
Since we don't want that, users cannot create bills from SAME claim more than once, we change their metadata at BCDB after bill creation.
However in dev mode, since we don't have ipfs we use a very simple json file to keep track of bill created/not-created files.
check controllers/hardcoded_files.json. Then set "created": values to true. After that you can be able to see claims again.
Actually in production, (which we use ipfs), it much more complicated, and you have to add new ipfs files to system, with right metadata's to see them.
I will explain all steps in meeting, and then we can update documentation together.
BCDB Python Driver
BCDB JS Driver
PUG-JS
HTML-to-PUG*
EXPRESS-DOCUMENTATION
- Developers changed Jade's name to PUG recently, so thats why that link directs to html2jade.org. It is not a mistake.
git remote add upstream https://github.com/jawadtahir/Allianz.gitgit fetch upstreamgit checkout mastergit merge upstream/master
git fetch upstream pull/{pull-request-id}/head:{pull-request-owners-branch-name}
Modify ./fabric-tool/fabric-scripts/hlfv1/composer/docker-compose.yaml in composer to have - CORE_LEDGER_HISTORY_ENABLEHISTORYDATABASE=true setting in environmt of peer 0