jt-nti / composer-devenv Goto Github PK

View Code? Open in Web Editor NEW

7.0 3.0 2.0 17 KB

Vagrant environment for developing business networks with Hyperledger Composer

License: Apache License 2.0

Shell 100.00%

composer-devenv's Introduction

composer-devenv

Vagrant environment to help get started with Hyperledger Composer.

Ingredients

You'll need to stock your machine with all these healthy ingredients if you don't have them already:

VirtualBox
Vagrant
- Note: composer-devenv requires Vagrant 2.0.3 or greater
Git

Method

To configure a development environment for the latest stable release of Composer (the 0.20.x stream), run the following commands:

git clone https://github.com/jt-nti/composer-devenv.git
cd composer-devenv
vagrant up

When the development environment has finished cooking, log in using:

vagrant ssh

Serving suggestion

Now that you have a working development environment, why not try one of the Composer tutorials?

Alternative toppings

To install specific versions of Composer, set a COMPOSER_VERSION environment variable before running vagrant up.

For example, to install an older version of Composer with Fabric 1.1 support (the 0.19.x stream) use:

COMPOSER_VERSION=0.19.14 vagrant up

Or on Windows:

set COMPOSER_VERSION=0.19.14
vagrant up

Supported COMPOSER_VERSION values:

latest for the latest 0.20.x release
Specific 0.16, 0.18, 0.19 or 0.20 version numbers
none to skip the Composer install

Cooking tips

Extra dishes

If you want to set up several VMs with different versions, or for different purposes, you can clone the composer-devenv repository into different directories. For example,

git clone https://github.com/jt-nti/composer-devenv.git composer-tutorial

Or simply copy an existing clone. The different directory names should show up in the VirtualBox UI after running vagrant up if you need to update the VM settings for any of your environments.

Clearing up

When you've finished with a development environment you can suspend it using vagrant suspend and resume later using vagrant up

Alternatively, if you've finished with Composer or want to start again, vagrant destroy will completely remove the virtual machine.

composer-devenv's People

Contributors

Stargazers

Watchers

Forkers

sunildsk shawnxiaoxiong

composer-devenv's Issues

Port collision auto-correction

It might be nice to include the auto_correct option for VM port forwarding

https://www.vagrantup.com/docs/networking/forwarded_ports.html#auto_correct

Add FABRIC_VERSION variable to vagrant's shell environment

The FABRIC_VERSION is automatically selected for the composer install script when bringing up the VM but it's currently not set in the vagrant user's environment

'can't modify frozen String' when running vagrant up

Getting the following error when running vagrant up with Vagrant 2.0.3

There was an error loading a Vagrantfile. The file being loaded
and the error message are shown below. This is usually caused by
a syntax error.

Path: /Users/jt/blockchain-dev/composer-devenv/Vagrantfile
Line number: 7
Message: RuntimeError: can't modify frozen String

Missing docker gpg key

Reported by @Thomas55777 in hyperledger/composer#3685

Yes, I am using VirtualBox and didn't realize that project existed. Thank you for pointing me in that direction, however I did get the follow error when running "vagrant up" seem it is unable to import the key needed to install docker:

default: Executing: /tmp/tmp.b1Qdeyr45T/gpg.1.sh --keyserver
default: hkp://p80.pool.sks-keyservers.net:80
default: --recv-keys
default: 58118E89F3A912897C070ADBF76221572C52609D
default: gpg: requesting key 2C52609D from hkp server p80.pool.sks-keyservers.net
default: gpgkeys: key 58118E89F3A912897C070ADBF76221572C52609D can't be retrieved
default: gpg: no valid OpenPGP data found.
default: gpg: Total number processed: 0
default: gpg: keyserver communications error: keyserver helper general error
default: gpg: keyserver communications error: unknown pubkey algorithm
default: gpg: keyserver receive failed: unknown pubkey algorithm

I checked http://p80.pool.sks-keyservers.net/ and few other key servers and that key doesn't appear to be in there. I fixed by editing the provision-root.sh file and replaced:

apt-key adv --keyserver hkp://p80.pool.sks-keyservers.net:80 --recv-keys 58118E89F3A912897C070ADBF76221572C52609D

with:

curl -fsSL https://apt.dockerproject.org/gpg | sudo apt-key add -
I got that from this blog: https://www.unixmen.com/how-to-install-wordpress-with-docker-on-ubuntu-16-04/

After that I reran "vargrant up --provision" and everything seemed to install correctly. Thank you very much for your help. It is greatly appreciated. I am glad to now be using Hyperledger with the proper setup even if it is only for dev.