For a seed node, you will need to install at minimum the Radicle CLI (`rad`),

and network daemon (`radicle-node`).

instructions there. You will have to download, verify and extract the binaries

and manuals to your preferred location.

### Creating a profile

data.

    rad auth --alias seed.radicle.example

</aside>

> **Tip**: If you wish to set a passphrase anyway, you will have to set the

Once your profile is initialized, a decentralized identifier (DID) will be

output. The part after the `did:key:` prefix is your Node ID. This is how your

You can view information about your Radicle profile by running `rad self`. The

`--nid` and `--alias` flags can be used to return the Node ID and alias.

---------------------

There are a couple of things we need to set up a seed node.

First, we must set the node's default *seeding policy*.

The seeding policy tells the node which repositories and forks to fetch

network. This address will be advertised to peers, allowing them to connect to

your seed node. Generally, this will be a DNS name with port `8776`, for

example `seed.radicle.example:8776`.

Here's an example minimal configuration file with a permissive seeding policy

```json

{

#### A *permissive* seeding policy

seed will try to have a full copy of all repository data available on the

network.

#### A *selective* seeding policy

all repositories, except the ones that are pre-configured to allow seeding.

repositories.

This is a good policy for communities, teams, companies and individuals who

#### Setting a repository's seeding policy

    rad seed rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5

This will override the default `block` rule for this one specific repository.

    rad unseed rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5

To view the policy of a specific repository, use the `rad inspect` command. For

example:

This will return the default policy if you haven't set a specific policy for

that repository.

### Your external address

Now that you've configured your seeding policy, it's time to set your node's

to your node. Though a single address is sufficient, you are free to set up

to 16 external addresses.

You'll find this setting in your configuration file, under

`node.externalAddresses`. External addresses are JSON strings of the form

`<host>:<port>`, for example `seed.radicle.example:8776`, where `<host>` is a

```json

{

### Your node address

For others to be able to connect to your node directly, they need your *Node

If you've configured one or more external addresses, simply entering the

following command from the `seed` user will output your node addresses:

`rad node connect <address>`, or by adding your address to their configuration,

under the `node.connect` field.

-----------------

Before setting up your node as a system service, it's a good idea to run it

once to make sure everything is working properly. Enter the following command

    exit

### Configuring your node's system service

Make sure it fits your needs by editing the file directly, or creating an

override using `systemctl edit`.

> user, for security reasons. This is already the case in the above service

> file.

### Changing your node's configuration

If you change your node's configuration while the node is running, you'll

First, verify that the new configuration is valid by running `rad config`, then

restart your node with:

this point onwards, if you chose to disable the `seed` user's shell, you'll

have to run all commands via `sudo`, like we've been doing so far.

>

>     alias rad='sudo -u seed -- rad'

### Firewalls

> using something like `iptables`, though this is out of scope for this guide.

Running the HTTP Daemon

actively and continuously discovers and replicates repositories on the network,

based on your seeding policy. This node allows users to collaborate, host,

The HTTP Daemon is a background process that functions as a *gateway* between

the Radicle protocol and the HTTP protocol. It is configured to have direct

<https://app.radicle.xyz>, it needs to respond to HTTPS requests. To do this,

we recommend using [Caddy][caddy].

install. If you are using Debian or Ubuntu, you can run:

    apt-get install caddy

[guide][caddy-guide] instead.

If everything worked, you should now have HTTPS support for your daemon. To

    curl https://seed.radicle.garden/api/v1

> outside, try running `systemctl reload caddy` after you've updated the

> configuration.

--------------

If you got this far, congratulations, you now have a Radicle seed node up

and running!