Skip to content

Command-line tools


The KDK CLI (a.k.a. kli) is a multiplexer for usual git/yarn commands used when developing KDK-based applications. It allows to easily clone, install, link, unlink, switch branch on all modules and application using a single command.


Production version:

yarn install -g @kalisio/kli

Or to use the master branch locally:

git clone
cd kli
yarn install
yarn link


The CLI relies on a workspace file defining the dependency tree between your KDK-based application and modules like this:

module.exports = {
  kdk: {
    dependencies: [],
    branches: ['master', 'test']
  kApp: {
    application: true,
    dependencies: ['@kalisio/kdk'],
    branch: 'master'

Each key is a git repository, i.e. a module, monorepo or application, with the following available properties:

  • dependencies: list of dependent (KDK-)based modules if any
  • branch: branch the module should be forced on whatever the target branch of the CLI
  • branches: list of branches the module is available on (if the target branch of the CLI is not included it will be skipped)
  • application: indicates if this is the main KDK-based application module, i.e. it has an api subfolder
  • path: relative path to the repository on the local disk
  • organization: GitHub/GitLab organization the repository belongs to
  • output: the name of the repository folder on the local disk
  • url: the root URL to the remote git repositories (if not given will be


The branch option can also target a git tag, typically fo production releases.


All operations will take effect in the current working directory so that subdirectories named according to modules will be created or expected to already exist.

// Will clone all repositories
kli workspace.js --clone
// Will install dependencies in all modules and application
kli workspace.js --install
// Will perform link between required modules and application
kli workspace.js --link
// Will perform unlink between required modules and application
kli workspace.js --unlink
// Will perform branch switching on all modules and application having the given target branch
kli workspace.js --branch test
// Will perform branch switching on all modules and application using the specified branch in workspace
kli workspace.js --switch


This CLI assumes git and yarn are already globally installed on your system.


By default all Git operations target the kalisio organization, you can change this for the whole workspace using the organization CLI option or on specific modules only using the organization option in the workspace file. Like this you include modules coming from a separate organization but used as dependencies of the project owned by the main organization of the project.


All operations are performed relative to the CWD by default, you can change this for specific modules only using the path option in the workspace file providing a module path relative to the CWD. Like this you can for instance have modules coming from a separate organization isolated into their own directory.

Sample workspaces for our application template, Kano and Kalisio Crisis are provided in the kli repository.

Full CLI usage is the following:

Usage: index <workspacefile> [options]

  -V, --version                      output the version number
  -o, --organization [organization]  GitHub organization or GitLab group owing the project (default: "kalisio")
  -u, --url [url]                    Git server base URL (default: "")
  -d, --debug                        Verbose output for debugging
  -c, --clone [branch]               Clone git repositories (with optional target branch) for all modules
  -p, --pull                         Pull git repositories for all modules
  -i, --install                      Perform yarn install for all modules
  -l, --link                         Perform yarn link for all modules
  -ul, --unlink                      Perform yarn unlink for all modules
  -b, --branch <branch>              Switch to target git branch in all modules where it does exist
  -s, --switch                       Switch all modules to the default git branch specified in workspace (if any)
  -m, --modules <modules>            Comma separated list of modules from the workspace to apply command on
  -h, --help                         output usage information

Working on multiple versions

In order to be able to switch easily between different versions of NodeJS you usually use a version manager like n/nvm under Linux/Mac or nvm under Windows. However, as links are global to a Yarn installation it can be tricky to switch between different versions of the same repository using different NodeJS versions, e.g. KDK on master branch running under NodeJS v12 and KDK on another branch running under NodeJS v16.

Although you can have a single local KDK repository and switch between the branches we do not recommand it. Indeed, each time you will switch you will also have to reinstall all the dependencies for the new NodeJS version, which can be cumbersome and has proven to be error-prone for package managers. Moreover, the branch names between the different repositories in a complex architecture might not be consistent. Last but not least, sometimes the repositories themselves might change their names or location between different versions.

In a nutshell, we recommand creating a different workspace for your application and clone each repository in a different folder for each version. This way it is far more easier to switch from one version to another, before switching to a new version you simply need to unlink the previous version workspace:

// We are currently using NodeJS v12
cd nodejs12
kli workspace-nodejs12.js --link
// Start working with NodeJS v16
kli workspace-nodejs12.js --unlink
nvm use 16.0.0
cd nodejs16
kli workspace-nodejs16.js --link


Gitrob is a tool to help find potentially sensitive files pushed to public repositories on Github. Simply run it using a GitHub token and a target user or organisation: gitrob -github-access-token XXX kalisio.

Then you can open the WebUI at http://localhost:9393 and see what's going on.


We use it to launch processes in the background on servers, which won't be killed when closing the ssh session.

Screen can also do the job


To track logs currently written, Docker has an equivalent command.


Customizable Windows terminal.

To add new tasks right click on settings > Startup/Tasks, and add commands like this to open a new PowerShell at a given location: powershell.exe -new_console:t:"TaskName":d:D:\path-to-directory.

If you'd like the PowerShell to execute a script at launch time (e.g. to setup your environment variables): powershell.exe -noexit path-to-script new_console:t:"TaskName":d:D:\path-to-directory

To make a command executed by default right click on settings > Startup > Select it as named task.

It might be required to modify the execution policy, e.g. Set-ExecutionPolicy -ExecutionPolicy RemoteSigned.

Travis CLI

To encrypt a file in reliable manner use a Linux VM or container because this does not work under Windows. For example with

docker pull caktux/travis-cli
// Mount your project as volume
// Override the default entry point which automatically launch the travis CLI with provided arguments
// otherwise you cannot do multiple commands
docker run -it --name travis -v d:/Development/kalisio/kaabah:/project --entrypoint="" --rm caktux/travis-cli sh
$ travis login
$ travis encrypt-file ssh.pem

Add the output to your build script:

  - openssl aes-256-cbc -K $encrypted_12c8071d2874_key -iv $encrypted_12c8071d2874_iv -in ssh.pem.enc -out ssh.pem -d