Linking Devkit & GreenLight

The Development Kit provides a fully working platform you can add features to GreenLight on. As you may have noticed, the content of the packages/greenroom/greenlight folder is identical to the GreenLight repository. While working on new elements of the package, maintaining this synchronised state is mandatory, which could be achieved in two ways.

Linking the two repositories

When you have both the Devkit installed and the GreenLight repository cloned to your local working environment, it is recommended to make a symbolic link / junction between the two repositories. This way any changes you make while working on the Devkit instance are going to be reflected to your local package repository too.

If you choose to work with symlinks, you have to remove everything (except for .git) from your GreenLight package repository first.

Making a symlink / junction between GreenLight and Devkit

Linux

ln -s /path/to/greenlight /path/to/devkit/packages/greenroom/greenlight

Windows

mklink /J /path/to/greenlight /path/to/devkit/packages/greenroom/greenlight

Manual synchronisation

As an alternative, whenever you finish a new feature in the Devkit, copying the whole content of the packages/greenroom/greenlight folder to the root of your GreenLight repository could work as well. Still, in order to avoid synchronisation mistakes, if it is possible, make sure you work using the first method.