The application developed during this milestone interacts with several of Fennel Protocol’s component services in order to provide a convenient user interface from which other domain-specific apps can be derived. As a result, you’ll need fennel-protocol, fennel-cli, fennel-app, and fennel-api running in parallel to test this iteration.

• Some cleanup to cut down on the number of local services is planned, but the current parallel development path will require the following for now.
• IF AT ANY TIME you get an error saying that “account is null”, just generate a wallet or import one you’ve already created.

👋 Getting Started

There are three backend applications that communicate with the web application. The following is a guide for getting each of those applications setup. The links to the repositories are provided in the header.

‣

First, run Fennel-Protocol. The easiest way is to run

docker-compose up -d

or to use our setup scripts:

./scripts/setup.sh
./scripts/build-run.sh

This will start the blockchain node that forms the core of the Fennel software distribution.

‣

Next up is the message server. This is used for off-chain communication and exposes a RESTful API.

You’ll need Python, Pip, and virtualenv installed, or more conveniently to use docker-compose to run the service.

There is a known issue under MinGW/Python for Windows which causes a dependency issue on Windows. Therefore, do not attempt to run on Windows.

If you’re running the API service outside of Docker on Linux or macOS, run

virtualenv venv
source ./venv/bin/activate
pip install -r requirements.txt
./runner.sh all-run