Diverse adjustments in the guides — radicle.xyz

rad:z371PVmDHdjJucejRoRYJcDEvD5pp

Radicle website including documentation and guides

Diverse adjustments in the guides

Merged levitte opened 8 months ago

in the seeder guide, seed.radicle.garden was used as an example domain, this got changed to seed.example.com.
seed.radicle.xyz and seed.radicle.garden were mentioned all over the guides, where iris.radicle.xyz and rosa.radicle.xyz are now the more relevant names.

seed.radicle.xyz is left untouched where it’s mentioned as an example of a selective seed, and where it’s used as the HTTPS source for repositories and files distributed by the Radicle team.

3 files changed +13 -12 908c756b → 68937bbb

modified _guides/protocol.md

@@ -325,7 +325,7 @@ an address book.

 Radicle's reference implementation is pre-configured with two [bootstrap
 nodes][bootstrap] that are connected to if the address book is empty:
 [seed.radicle.garden][] and [seed.radicle.xyz][]. These are nodes run by the
 [iris.radicle.xyz][] and [rosa.radicle.xyz][]. These are nodes run by the
 Radicle team and have large address books that are shared with connecting
 peers.

@@ -823,7 +823,8 @@ collaboration.

 [git-v2]: https://git-scm.com/docs/protocol-v2
 [Tor]: https://torproject.org/
 [Ed25519]: https://ed25519.cr.yp.to/
 [seed.radicle.garden]: https://app.radicle.xyz/nodes/seed.radicle.garden
 [iris.radicle.xyz]: https://app.radicle.xyz/nodes/iris.radicle.xyz
 [rosa.radicle.xyz]: https://app.radicle.xyz/nodes/rosa.radicle.xyz
 [seed.radicle.xyz]: https://app.radicle.xyz/nodes/seed.radicle.xyz
 [reverse-dns]: https://en.wikipedia.org/wiki/Reverse_domain_name_notation
 [tuf]: https://theupdateframework.github.io/specification/latest/

modified _guides/seeder.md

@@ -230,7 +230,7 @@ A *permissive* or "open" policy is said to be *fully-replicating*, meaning your

 seed will try to have a full copy of all repository data available on the
 network.
 An example of a node with this policy is `seed.radicle.garden`, a node operated
 An example of a node with this policy is `iris.radicle.xyz`, a node operated
 by the Radicle team, for the Radicle community.
 This is a good default for seeders who want to support the network without

@@ -587,7 +587,7 @@ Finally, edit or create the `Caddyfile` at `/etc/caddy/Caddyfile`, and *replace*

 its contents with the following configuration, using the correct domain name
 for your seed:
     seed.radicle.garden {
     seed.example.com {
         reverse_proxy 127.0.0.1:8080
     }

@@ -603,13 +603,13 @@ If you encounter issues setting up Caddy, you can try following their

 [guide][caddy-guide] instead.
 If everything worked, you should now have HTTPS support for your daemon. To
 check, run the following command, replacing `seed.radicle.garden` with your
 check, run the following command, replacing `seed.example.com` with your
 seed's domain:
     curl https://seed.radicle.garden/api/v1
     curl https://seed.example.com/api/v1
 You should now be able to visit your seed node via any Radicle web frontend as
 well. For example, <https://app.radicle.xyz/nodes/seed.radicle.garden>.
 well. For example, <https://app.radicle.xyz/nodes/seed.example.com>.
 > On some distributions, installing `caddy` will start the system service
 > automatically. If you're not able to connect to your HTTP daemon from the

modified _guides/user.md

@@ -445,17 +445,17 @@ Note that your new repository will only be replicated by nodes that you are

 connected to and either have an open seeding policy, or follow you. Seeding
 involves both hosting the repository and synchronizing changes with other
 nodes. In the early stages of the Radicle network, all public repositories are
 automatically seeded by `seed.radicle.garden` which is a *public seed node*
 run by the core team.
 automatically seeded by `iris.radicle.garden` and `rosa.radicle.garden` which
 are *public seed nodes* run by the core team.
 <!-- TODO: Talk about seeding policies and following -->
 <aside class="span-2"> <strong>Seed nodes</strong> are always-on machines that
 significantly enhance the network’s capacity to provide continuous access to
 repositories. They can vary in their seeding policies, from public seed nodes
 like <code>seed.radicle.garden</code> that openly seed all repositories, to
 community seed nodes that selectively seed repositories based on rules
 established by their operators. </aside>
 like <code>iris.radicle.xyz</code> and <code>rosa.radicle.xyz</code> that
 openly seed all repositories, to community seed nodes that selectively seed
 repositories based on rules established by their operators. </aside>
 You don't *have* to trust or rely on our public seed node. You can run
 your own. As more people run them, Radicle becomes more resilient and