Repository URL to install this package:
Version:
0.6.0 ▾
|
.. |
dist |
node_modules |
LICENSE |
README.md |
package.json |
CLI tool to spin up Docker cluster of Bee nodes for advanced testing and/or development
Warning: This project is in beta state. There might (and most probably will) be changes in the future to its API and working. Also, no guarantees can be made about its stability, efficiency, and security at this stage.
Requirements: Docker
$ npm install -g @ethersphere/bee-factory
# This spins up the cluster for specific Bee version and exits $ bee-factory start --detach 1.5.1 # The spins up the cluster using Bee version configured in external places. See bellow for options where to place it. $ bee-factory start --detach # This attaches to the Queen container and displays its logs $ bee-factory logs queen --follow # This stops the cluster and keeping the containers so next time they are spinned up the data are kept # but data are not persisted across version's bump! $ bee-factory stop # You can also spin up the cluster without the --detach which then directly # attaches to the Queen logs and the cluster is terminated upon SIGINT (Ctrl+C) $ bee-factory start 1.5.1
For more details see the --help
page of the CLI and its commands.
You can omit the Bee version argument when running bee-factory start
command if you specify it in one of the expected places:
package.json
placed in current working directory (cwd) under the engines.bee
property..beefactory.json
placed in current working directory (cwd) with property version
.Bee Factory as the NPM package that you can install, like mentioned above, works in a way that it orchestrates launching Bee Factory Docker images
in correct order and awaits for certain initializations to happen in correct form. These Docker images are automatically built with our CI
upon every new Bee release, so you can just specify which version you want to run (starting with 1.5.1
version) as part of the start
command.
If for some reason you want built your own images, that is possible but discouraged and not supported (here be dragons) using the scripts in the generator
subfolder.
Upon building and publishing these images you can consume them using with Bee Factory with the --repo
flag.
There are some ways you can make this module better:
You can run the CLI while developing using npm start -- <command> ...
.