GNUNET-SETUP(1)

✨ NAME ✨

gnunet-setup β€” it's a gtk interface for configuring GNUnet, and honestly? it's giving GUI πŸ’…


🌸 SYNOPSIS 🌸

gnunet-setup [OPTIONS]

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so gnunet-setup is a gtk+ based GUI for configuring GNUnet. that's the whole vibe. no cap.

The first time you run gnunet-setup, your goal is usually gonna be configuring the peer β€” aka the set of processes that always run in the background. those processes should run as user "gnunet", so bestie, run gnunet-setup as user "gnunet" for this step too. use the -e option to enable automatic privilege escalation using gksu (if your system supports it, iykyk). alternatively you can of course run gnunet-setup from the "gnunet" system user account or even as "root". if you see a tab called "General", congrats queen, you started gnunet-setup correctly to configure the peer πŸŽ€.

Now you should be able to configure which subsystems of GNUnet you want to enable, which databases to use, and what your network configuration looks like. once those steps are done, you should be able to start your peer using "gnunet-arm". slay.

It is recommended that "/etc/gnunet.conf" should be a world-readable copy of the peer's GNUnet configuration. note that GNUnet configuration files (as generated by gnunet-setup) only contain those values that differ from the defaults. also note that "gnunet-arm" will by default look for a configuration in "$HOME/.config/gnunet.conf" (or, "$XDG_CONFIG_DIR/gnunet.conf" if "$XDG_CONFIG_DIR" is set); thus, if your configuration is in "/etc/gnunet.conf", you have to pass "-c /etc/gnunet.conf" to gnunet-arm or set "$XDG_CONFIG_DIR" to "/etc/". don't skip this part, it's literally the whole plot πŸ™ˆ

  • -c FILENAME, --config=FILENAME β€” load config file (default: ~/.config/gnunet.conf)
  • -e, --elevate-privileges β€” try to elevate privileges to run gnunet-setup as user "gnunet". this option is only available if libgksu-support was found on your system. it is ignored if gnunet-setup is run as user "root" or "gnunet" already. if "gksu" fails, gnunet]-setup is run as the current user.
  • -h, --help β€” print help page
  • -v, --version β€” print the version number

πŸ‘‘ NOTES πŸ‘‘

Many options in gnunet-setup are documented online. access the online help by first selecting the respective widget and then clicking on the link at the bottom of the dialog. cute, right? πŸ’–

Exiting gnunet-setup (by closing the window or pressing ESCape) always saves the current configuration to disk. so like, don't panic-close it thinking nothing happened, bestie 😭

πŸ“ FILES πŸ“

  • ~/.config/gnunet.conf β€” User's GNUnet configuration file

🧚 REPORTING BUGS 🧚

Report bugs by using mantis <https://bugs.gnunet.org/> or by sending electronic mail to <gnunet-developers@gnu.org>. found a bug? spill, we're listening 🫢


🌈 SEE ALSO 🌈

gnunet-arm(1), gnunet.conf(5)


and that's the tea πŸŽ€ this was the GNUNET-SETUP(1) page from the General Commands Manual, brought to you by GNUnet and dated 25 Oct 2012. go configure something iconic, bestie πŸ’…βœ¨