Uqda can run in one of two modes: with a configuration file, or in autoconfigure mode.
A static configuration file simplifies most setups as it allows you to keep the same keypair (and therefore IP address), maintain a list of peers and so on. For most users this will be the recommended configuration.
However, autoconfigure mode allows you to quickly start Uqda using sane-ish default settings, with uqda -autoconf. In this mode, Uqda will automatically attempt to peer with other nodes on the same subnet but will not attempt to connect to public peers by default. It also generates a random set of keys each time it is started, and therefore a random IP address each time.
You can generate a configuration file in the following ways:
The configuration file is typically located in /etc/uqda/uqda.conf or /etc/uqda.conf depending on your platform.
Uqda can accept a configuration file either through stdin or by being given a path on the filesystem to a configuration file:
Uqda can be configured to connect to other peers by adding entries into the Peers configuration section. At startup, Uqda will attempt to open a connection to these peers.
A peering URI will look similar to one of the following:
By default, only link-local auto-peering is enabled. This connects devices that are connected directly to each other at layer 2, including devices on the same LAN.
If you are unable to find nodes in the nearby area, you can add public peers to your configuration. See the Configuration Reference for more details.
Information about the various options in the configuration file can be found here.