Comment on page
Swiss knife to start automate any kind of routine work.
- DevOps, as fbl can make the flow control deployment an easy task. We already use FBL to make K8s deployments.
- Developers, who need to automate their routine tasks. We use FBL to create CLI wizards to share with other teams to execute one time tasks on environments we have no direct access.
- Managers. We use FBL to gather time sheet reports from multiple sources to create monthly reports on user activities.
- Anyone who just wants to automate his routine work a bit.
FBL allows to write both simple and really complex scenarios, where tasks can be spread into different streams. Streams can be executed in parallel and once all are done - another stream will start of proceed, depending on your needs.
FBL is not oriented to resolve just one particular thing, but to resolve any kind of automation task with reach set of plugins. By itself FBL exposes few handy plugins that can help you to start the automation flow. Plugins from FireBlink or any 3rd party developer can easily be integrated into your flows.
Found no suitable plugin? No problem - either create it yourself or contact us to create one for you. We also open to help with writing automation scenarios of any kind and complexity. We provide a handy template to start with plugin development - fbl-plugin-template
Want to share your flow with others? No problem, just create a tarball (*.tar.gz archive) with index.yml file inside and share with others. Packaged flows can be used directly inside other flows or invoked via CLI (remote URLs are supported).
Just run following command in your terminal to install fbl:
npm i -g fbl
To get list of available CLI arguments run:
- FBL_HOME - defines alternative
fblcan store cached packages (downloaded tarballs), etc. Default value is
.fblinside user home directory, e.g. on unix systems: