The Fluence Labs Developer Hub

Welcome to the Fluence Labs developer hub. You'll find comprehensive guides and documentation to help you start working with Fluence Labs as quickly as possible, as well as support if you get stuck. Let's jump right in!

Should you have any questions, feel free to join our Discord or Telegram!

Get Started

Launching a node

Basic setup

Fluence node comes in a docker container fluencelabs/fluence. It needs to know its external IP address and be directly available on the network (i.e., no NAT involved).

docker run -p9999:9999 -p7777:7777 fluencelabs/fluence -x $YOUR_EXTERNAL_IP

Managing logs

Logging can be enabled or disabled on a per-scope basis via the RUST_LOG environment variable passed to the container. For example:

docker run -e RUST_LOG="info,particle_server::behaviour=debug" fluencelabs/fluence

Here default log level for everything will be info, and for the particle_server::behaviour scope, it will be set to debug.


Configuration file Config.toml placed inside Docker container at /.fluence/Config.toml. Default configuration can be viewed on github.

Path to config file can be set by passing -c /path/to/Config.toml on node run:

docker run fluencelabs/fluence -c /path/to/Config.toml

Directory structure

By default, a Fluence node is configured to store all data inside the /.fluence directory. This is configured in Config.toml like this:

root_key_pair = "./.fluence/secret_key"
services_base_dir = "./.fluence/services"
stepper_base_dir = "./.fluence/stepper"
certificate_dir = "./.fluence/certificates"

Updated 2 months ago

Launching a node

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.