Skip to content

Deploy Worker Node

A worker node represents a domain — an organization that owns data and executes tasks locally, enforcing its own policies.

Terminal window
branectl download services worker -f
Terminal window
# Backend (how to execute containers)
branectl generate backend -f -p ./config/backend.yml local
# Proxy
branectl generate proxy -f -p ./config/proxy.yml
# Policy secrets and database
branectl generate policy_secret -f -p ./config/policy_deliberation_secret.json
branectl generate policy_secret -f -p ./config/policy_expert_secret.json
branectl generate policy_db -f -p ./policies.db
# Node configuration (generate last)
branectl generate node -f worker <YOUR_HOSTNAME> <LOCATION_ID>

Replace <YOUR_HOSTNAME> with the address reachable by other nodes, and <LOCATION_ID> with this domain’s unique ID (must match the central node’s infra.yml).

./
config/
certs/
backend.yml
proxy.yml
policy_deliberation_secret.json
policy_expert_secret.json
node.yml
policies.db
target/
release/
Terminal window
branectl generate certs -f -p ./config/certs server <LOCATION_ID> -H <HOSTNAME>

Share the ca.pem file with the central node administrator.

By default, all requests are denied. Set up policies before starting:

Terminal window
branectl generate policy_token <EXPERT_NAME> <DOMAIN_ID> 30d \
-s ./config/policy_expert_secret.json

See the Policy Guide for writing policies.

Terminal window
branectl start worker

Monitor: docker ps

Terminal window
branectl stop worker