Skip to content
Switch branches/tags
Go to file
Cannot retrieve contributors at this time

Mojaloop Onboarding


  1. Installing CLI Tools
  2. Non-CLI Tools
  3. Development Workflow
  4. Contributing to a Specific Sub Project
  5. Other Useful Links
  6. Common Errors & FAQs

Installing CLI Tools

Building and Running Mojaloop from source requires the following tools:

  1. brew (MacOS) [todo: windows package manager]
  2. docker
  3. docker-compose
  4. npm and nvm(optional)

1. brew (MacOS)


Brew is a package manager for macOS. The simplest installation method is:

/usr/bin/ruby -e "$(curl -fsSL"


[todo: make sure tools are available on apt and yum]

Most of the tools we install with brew are available on existing linux package managers, such as apt and yum. That doesn't stop you from using brew on Linux if you'd like. You can follow the Official Linux Installation Guide to do so.


[todo: find alternative]

2. docker

We use docker to build reliable images of the Mojaloop components, as well as install and run other developer tools such as MySQL and Kafka without requiring the overhead of installing a bunch of stuff.


Follow the Docker for Mac installation guide here


Install Docker for Ubuntu here, or Docker for CentOS here.
You can also install from docker binaries if your flavor of Linux is not supported here.


Follow the Docker Desktop for Windows installation guide here.

3. docker-compose

Docker Compose is a tool for easily running multiple docker containers at once. It can be used to replace cumbersome docker run commands with a docker-compose.yml file.


If you installed Docker using Docker for Mac, then docker-compose is already installed. Run:

docker-compose --version

To verify its installation.


Follow this guide to install docker-compose on your linux machine.


If you installed Docker using Docker Desktop for Windows, then docker-compose is already installed. Run:

docker-compose --version [todo: confirm]

To verify its installation.

4. npm and nvm

The preferred approach (especially if you use node on multiple projects) is to use nvm (Node Version Manager) to manage your global nodejs versions. There are other tools available to manage your node versions, but nvm is the lightest weight, and tends to need the least amount of configuration.


nvm is a version manager for node. It's not strictly required, but it will make it easier to switch from one node version to another.


Ensure that you have curl or wget installed, and run:

curl -o- | bash 

or with wget:

wget -qO- | bash

Then follow the rest of the MacOS installation steps.


Use a brew package manager

brew install nvm

and follow instructions shown in terminal to properly setup your shell environment for nvm.

Or download and install the nvm installer with curl:

curl | bash

If the install was successful, run nvm --version which should return the version of nvm installed.

Install and use the latest LTS version of NodeJS: (at the time of writing this is 10.15.3)

nvm install --lts
nvm use --lts


Set Up NVM In ~/.bash_profile, .zshrc, or .profile:

For NVM to work the next time you open your shell, you need to make sure that following exists in your .bash_profile, .zshrc, or .profile:

export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/" ] && . "$NVM_DIR/" # This loads nvm

If you don't have a ~/.bash_profile, you can create one with:

touch ~/.bash_profile

And using a your text editor of choice, add the following:

export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/" ] && . "$NVM_DIR/" # This loads nvm

You will need to run source ~/.bash_profile, or restart your shell for these changes to take effect.


NPM is the node package manager. It allows us to install and manage the dependencies for each of the sub-projects. We also use npm as the entry point for many different commands, such as running tests [finish]

If you installed nvm above, you can skip this step, as npm will already be installed.


Use homebrew to install node and npm together.

brew install node

If you have already installed nvm (see above) you can skip this step. Elsewhere you can have multiple Node.js instances and it could bring some problems in future.

#Add the LTS Repo
sudo apt-get install curl python-software-properties
curl -sL | sudo -E bash -

sudo apt-get install nodejs

For other flavours of Linx, follow the installation guide here



Non-CLI Tools

  1. Github
  2. Postman
  3. Zenhub
  4. Javascript IDE (optional)
  5. MySQLWorkbench (optional)

1. Github

All of the Mojaloop repos are available on Github. While you don't need a GitHub account to download and play around with the code, you must have your own GitHub account set up in order to contribute to Mojaloop.

In order to contribute to a given repo, you should first make a fork of the repo in your own account, and submit a pull request from that fork. For more information about contributing, refer to the Creating new Features guide in the Mojaloop Documentation.

2. Postman

Postman is a tool for exploring and testing APIs.

To install Postman, follow these instructions: Get Postman

Alternatively on Ubuntu you may run:

wget -O postman.tar.gz
sudo tar -xzf postman.tar.gz -C /opt
rm postman.tar.gz
sudo ln -s /opt/Postman/Postman /usr/bin/postman

Postman Setup

There are already a number of ready-made Mojaloop Postman collections in the Postman Repo.

git clone

You can then import these collections into your Postman:

  • open Postman
  • click Import and then Import File
  • navigate to the postman directory and select Mojaloop.postman_collection.json

Each of the collections depend on an environment to be imported as well.

  • open Postman
  • click Import and then Import File
  • navigate to the postman/environments directory and select the most appropriate environment for your mojaloop setup. For example, when running mojaloop Locally, import and use the MojaloopLocal.postman_environment.json environment.

3. Zenhub

Zenhub is a Project Management Plugin for GitHub. It adds some helpful features such as Kanban, easier project management workflows, etc.


4. Javascript IDE (Optional)

When developing for Mojaloop, you may wish to use a Javascript IDE or a simple text editor. There are plenty available out there, including:

5. MySQLWorkbench (Optional)

MySQL Workbench is a GUI Based database management tool.

We will only cover the installation of MySQLWorkbench in this guide. For using MySQLWorkbench with a given sub-project, refer to the specific on-boarding guide in the respective project.


use brew package manager

brew cask install mysqlworkbench


  • Go to this page here
  • Scroll down the page > select macOS for the operating system > Download

Note: this version of MySQLWorkbench is compatible with Mojave (10.14) and High Sierra (10.13)


For debian based linux, you can install using apt:

sudo apt install mysql-workbench

For other linux flavours follow the instructions here


  • Go to this page here
  • Scroll down the page > select Windows for the operating system > Download
  • Run the installer and open MySQL Workbench

Development Workflow

While the workflow will change for each Mojaloop sub-project, these steps will generally applicable to any part of the codebase that you end up working on. For more information, take a look at the Creating new Features guide, but in summary:

For each sub-project:

git clone<your_username>/<forked_repo>.git && cd <forked_repo>
git remote add mojaloop<original_repo>.git

For each new feature:

git checkout -b <branchType>/<issue#><issueDescription>

More information about formatting branches here: Creating new Features

Commiting code changes

npm install  # installs the dependencies
npm run test # runs the local unit tests
git commit -am "<Commit message>"
git push

If you need help writing good commit messages, take some inspiration from this post.

Merge into Mojaloop Once a feature is complete, you can create a PR from your Feature Branch into the master branch of the Mojaloop repository.

Contributing to a Specific Sub Project

Now that you have completed this onboarding guide, you are now ready to follow the installation and setup steps for each individual mojaloop sub-project.

Follow the Onboarding guides for each sub project here:

Other Useful Links

Common Errors & FAQs

  • None yet. If you run into a problem or have a question, ask away and we can add to this list for future reference.