[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Minimum viable GNS deployment
From: |
Christian Grothoff |
Subject: |
Re: Minimum viable GNS deployment |
Date: |
Thu, 3 Feb 2022 22:58:29 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 |
Hi,
Many GNUnet services are started 'on demand', so there is actually no
need to explicitly enable them. To get the minimum set of services, you
mostly need to disable the 'IMMEDIATE_START' option of applications you
do not want. Those will likely be the ones in the following sections:
RPS, REST and FS. Everything else is either a dependency of GNS or part
of GNS.
You can do this by running
$ gnunet-config -s $SECTION -o IMMEDIATE_START -V NO
for each of the three sections I named.
Happy hacking!
Christian
On 2/3/22 8:18 PM, Chris Joel wrote:
> Hello,
>
> I'm interested in trying out GNS as a name system for an application I'm
> making. I have played around a little bit with Gnunet, but I'm still
> very new to it and I still have a lot to learn about its architecture
> and configuration.
>
> I understand that Gnunet runs many services that have a hierarchical
> dependency relationship. I was wondering two things:
>
> What is the minimum set of services needed to run a viable GNS peer?
>
> ...and...
>
> What is the best way to configure Gnunet to only run those services
> needed for GNS?
>
> Kind regards,
>
> Chris Joel