The goal is to run c-lightning with plugins in a local testing cluster. For my cluster I use Simverse. Simverse allows for additional command line arguments to be passed to
lightningd, so it should be possible to run
lightningd with the
Let's first clone our plugin. We will be using one of the plugins that are available through Lightningd on Github.
cd ~\simverse\_repos git clone https://github.com/lightningd/plugins.git --depth 1
We put the plugin in the
_repos folder, because it is assumed that the plugin is there when the cluster is being build. (Also: throughout this article we assume your simverse folder is inside your home folder. If that is not the case, adjust it accordingly)
Since all nodes in Simverse run inside Docker containers, that plugin-file should be made available inside the Docker context folder. The
_repos folder is not part of that context (each container gets its own context) so we have to copy the file from the
_repos folder to the Docker context folder. Luckily Simverse works with the concept of recipes. A recipe describes how your cluster should look like. A recipe is a bash script that uses a library called cookbook that can be used to build your cluster step-by-step. Since it is "just" a bash script, you can do anything bash can do to tweak your cluster.
We will create a recipe that creates a cluster with three c-lightning nodes, running on a bitcoind back-end.