default:

	bundle exec jekyll build $(CONFIG)

	scripts/cleanup-svgs.sh assets/images/*.svg

publish: default

clean:

	@rm -rfv _site

baseurl: "/"

plugins:

title: "Radicle: the sovereign forge"

description: "The Radicle forge is an open source, peer-to-peer code collaboration stack built on Git."

fedi: "@radicle@toot.radicle.xyz"

explorer: "radicle.network"

# jekyll-feed configuration

feed:

Radicle's reference implementation is pre-configured with two [bootstrap

nodes][bootstrap] that are connected to if the address book is empty:

Radicle team and have large address books that are shared with connecting

peers.

[git-v2]: https://git-scm.com/docs/protocol-v2

[Tor]: https://torproject.org/

[Ed25519]: https://ed25519.cr.yp.to/

[reverse-dns]: https://en.wikipedia.org/wiki/Reverse_domain_name_notation

[tuf]: https://theupdateframework.github.io/specification/latest/

[noise]: http://www.noiseprotocol.org/noise.html

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

network.

by the Radicle team, for the Radicle community.

This is a good default for seeders who want to support the network without

allow repositories to be seeded*. This means that the node will ignore

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

unit file. Place it in `/etc/systemd/system/radicle-node.service` for it to

be found by `systemctl`:

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

override using `systemctl edit`.

As with `radicle-node`, we can start by downloading an example `systemd` unit

file for the daemon:

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

override using `systemctl edit`.

🎊👾

[caddy]: https://caddyserver.com/

[caddy-guide]: https://caddyserver.com/docs/running#linux-service

[caddy-install]: https://caddyserver.com/docs/install

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

are *public seed nodes* run by the core team.

<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

openly seed all repositories, to community seed nodes that selectively seed

repositories based on rules established by their operators. </aside>

> Radicle's codebase hasn't yet undergone formal security audits. While we're

> confident in its security, undiscovered vulnerabilities may exist. If you

> encounter any issues, we encourage you to report them to

## 4. Embracing the Onion

> Radicle's codebase hasn't yet undergone formal security audits. While we're

> confident in its security, undiscovered vulnerabilities may exist. If you

> encounter any issues, we encourage you to report them to

[proto]: /guides/protocol/

[seeder]: /guides/seeder/

  💾

  <span class="release-loader"></span>

  <span>

    <span class="desktop dim">&middot; </span>

    <span id="release-commit" class="desktop"></span>

    <span id="release-timestamp" class="desktop"></span>

  const release = document.getElementById('release');

  release.classList.remove("hidden");

    .then(res => res.json())

    .then(data => {

      const version = data.version;

<meta name="fediverse:creator" content="{{ author.fedi | default: site.fedi }}" />

<noscript>

  <p>

    Browse the latest release at

  </p>

</noscript>

  <thead><th>Signer</th></thead>

  <tr><td>Key</td><td><code>ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIL460KIEccS4881p7PPpiiQBsxF+H5tgC6De6crw9rbU</code></td></tr>

  <tr><td>Fingerprint</td><td><code>SHA256:iTDjRHSIaoL8dpHbQ0mv+y0IQqPufGl2hQwk4TbXFlw</code></td></tr>

  <tr><td>Key</td><td><code>ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIBrJyJTwj/xG7F7qY0HDFXbb8A+xNNH8eILQ8hlvKW7/</code></td></tr>

  <tr><td>Fingerprint</td><td><code>SHA256:MOkcQvljDqQn8y+zlHFssx6gdH0rXdC+Wn88bsTPp6g</code></td></tr>

  <tr><td>Key</td><td><code>ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIEFsaRqAJ1r6bBFwlcWzJKN7DdjItQDumCNc0wqw6Dvk</code></td></tr>

  <tr><td>Fingerprint</td><td><code>SHA256:vV38nW5eSWfTMITdAoMCBOFzEEr0bDMXjSWHpwrpsKY</code></td></tr>

  <tr><td>Key</td><td><code>ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIFhK7CqgIIbSthoNn8ea32krOnMzC807Z+PpBkR2YOVj</code></td></tr>

  <tr><td>Fingerprint</td><td><code>SHA256:xX6bpr+AeF5G0wIvU8nLisgYRM6XjQVNJs3hkMGt+T0</code></td></tr>

</table>

<p id="radicle-httpd-release-header" class="loading">

<noscript>

  <p>

    Browse the latest release at

  </p>

</noscript>

  <thead><th>Signer</th></thead>

  <tr><td>Key</td><td><code>ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIEFsaRqAJ1r6bBFwlcWzJKN7DdjItQDumCNc0wqw6Dvk</code></td></tr>

  <tr><td>Fingerprint</td><td><code>SHA256:vV38nW5eSWfTMITdAoMCBOFzEEr0bDMXjSWHpwrpsKY</code></td></tr>

  <tr><td>Key</td><td><code>ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIPueml1FxzjvwbD7vRZfwoaoyuxLy0L+WLBwSNiVoJe5</code></td></tr>

  <tr><td>Fingerprint</td><td><code>SHA256:s/6EWLSAoeZWREZxj8vr6FtM6NaDjWhwsGB80eoaSzs</code></td></tr>

  <tr><td>Owner</td><td>rudolfs@osins.org</td></tr>

You can download the appropriate tarball for your operating system with:

For Radicle proper, and:

For Radicle HTTP Daemon.

and overwrite any existing Radicle binaries.

<script>

  function getRelease(name, urlBase, releaseId) {

      const releases = document.getElementById(`${releaseId}-releases`);

layout: none

permalink: /.well-known/security.txt

---

# Use `age` with `--recipients-file`.

# See also:

</span></em>

We are seeking talented people to join us in contributing to Radicle and this page lists open positions we are looking to fill.

Unsolicited applications, i.e., ones that fit none of the positions below, are also welcome.

Note that we currently are:

# Feedback

If you have feedback, join our [Zulip][zulip] or send us an email at

address are automatically posted to our [#feedback](https://radicle.zulipchat.com/#narrow/channel/392584-feedback)

channel on Zulip.

LORENZ="ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIFhK7CqgIIbSthoNn8ea32krOnMzC807Z+PpBkR2YOVj"

url() {

}

info() {

  printf "radicle $LORENZ\n" >> $signers

  # Verify that `$archive` was signed by a key in `$signers`, identified by the

  ssh-keygen -Y verify -f $signers -I "radicle" -n file -s "$archive.sig" < "$archive" || fatal "Invalid signature for $archive"

}