From e990342f85d5aa185c32116d5fe806fa28ed3658 Mon Sep 17 00:00:00 2001 From: Ruben Barkow Date: Wed, 16 Oct 2019 23:59:17 +0200 Subject: [PATCH] docs: replace alfred with respondd (#1842) --- docs/features/roles.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/features/roles.rst b/docs/features/roles.rst index 3af09c01..dcefe042 100644 --- a/docs/features/roles.rst +++ b/docs/features/roles.rst @@ -2,8 +2,8 @@ Roles ===== It is possible to define a set of roles you want to distinguish at backend side. One node can own one -role which it will announce via alfred inside the mesh. This will make it easier to differentiate -nodes when parsing alfred data. E.g to count only **normal** nodes and not the gateways +role which it will announce via respondd/announced inside the mesh. This will make it easier to differentiate +nodes when parsing respondd data. E.g to count only **normal** nodes and not the gateways or servers (nodemap). A lot of things are possible. For this the section ``roles`` in ``site.conf`` is needed::