Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
vms:webdev:fabric [2017/03/17 03:48]
admin [Fabric Components]
vms:webdev:fabric [2017/03/17 19:06] (current)
admin [Fabric Components]
Line 148: Line 148:
 <​code>​ <​code>​
 > npm install -g composer-cli > npm install -g composer-cli
 +</​code>​
 +
 +There was a problem with this install command: hashtable blocked the process.\\
 +A suggested solution on the Fabric Chat:
 +> So ... the root cause of my installation issues with `node-gyp` was the self-signed certificate in the chain
 +`node-gyp` doesn'​t honour the `strict-ssl=false` setting in `.npmrc`
 +> The workaround to get composer-cli to install was to run the following:
 +<​code>​
 +export NODE_TLS_REJECT_UNAUTHORIZED=0
 +</​code>​
 +before
 +<​code>​
 +npm install -g composer-cli
 </​code>​ </​code>​
  
Line 162: Line 175:
 > Cannot connect to the Docker daemon. Is the docker daemon running on this host? > Cannot connect to the Docker daemon. Is the docker daemon running on this host?
  
-This required to add the following in /​root/​.bashrc:​+This required to add the following in ''​/​root/​.bashrc''​:
 <​code>​ <​code>​
 export NVM_DIR="/​home/​sysadmin/​.nvm"​ export NVM_DIR="/​home/​sysadmin/​.nvm"​
 [ -s "​$NVM_DIR/​nvm.sh"​ ] && . "​$NVM_DIR/​nvm.sh" ​ # This loads nvm [ -s "​$NVM_DIR/​nvm.sh"​ ] && . "​$NVM_DIR/​nvm.sh" ​ # This loads nvm
 +</​code>​
 +
 +Also had to run a few commands //​manually//​ before I got it running (root in ''/​home/​sysadmin/​sample-applications/​packages/​getting-started''​):​
 +<​code>​
 +> docker pull hyperledger/​fabric-baseimage:​x86_64-0.1.0
 +> scripts/​download-hyperledger.sh
 +> scripts/​start-hyperledger.sh
 +> npm run deployNetwork /​home/​sysadmin/​sample-applications/​packages/​getting-started
 </​code>​ </​code>​