Daniel Norman
eee5cb8d8c
Each COB change names an identity commit in its `Rad-Resource` trailer. Patches and issues check the rights of the author against the document in that commit. Nothing checked that the commit is a revision of the repository identity. Any user could write a commit with a document that names them as a delegate, cite it, and act as a delegate. - Add `Identity::is_accepted`, which follows each revision's parent back from `rad/id`, so a change that cites the head costs one blob read - Add `ReadRepository::identity_revision_doc`, which returns the document of an accepted identity revision only - Use it in `Op::identity_doc`, so a change with any other resource gets no identity document and is rejected - Document that `identity_doc_at` does not check the commit - Test forged resources on patches and issues, and the accepted chain Accepted revisions form a chain, because a revision is only adopted if its parent is the current revision. Callers synchronize `rad/id` with the current revision after identity writes, so the chain holds every accepted revision.
❤️🪵
Radicle Heartwood Protocol & Stack
Heartwood is the third iteration of the Radicle Protocol, a powerful
peer-to-peer code collaboration and publishing stack. The repository contains a
full implementation of Heartwood, complete with a user-friendly command-line
interface (rad) and network daemon (radicle-node).
Radicle was designed to be a secure, decentralized and powerful alternative to code forges such as GitHub and GitLab that preserves user sovereignty and freedom.
See the Radicle home page for general information, and the Zulip chat to talk to the project.
See the Protocol Guide for an in-depth description of how Radicle works.
Installation
Requirements
- Linux or Unix based operating system.
- Git 2.34 or later
- OpenSSH 9.1 or later with
ssh-agent
📀 From binaries
Requires
curlandtar.
Run the following command to install the latest binary release:
curl -sSf https://radicle.dev/install | sh
Or visit our download page.
📦 From source
Requires the Rust toolchain.
You can install the Radicle stack from source, by running the following commands from inside this repository:
cargo install --path crates/radicle-cli --force --locked --root ~/.radicle
cargo install --path crates/radicle-node --force --locked --root ~/.radicle
cargo install --path crates/radicle-remote-helper --force --locked --root ~/.radicle
Or directly from our seed node:
cargo install --force --locked --root ~/.radicle \
--git https://seed.radicle.dev/z3gqcJUoA1n9HaHKufZs5FCSGazv5.git \
crates/radicle-cli crates/radicle-node crates/radicle-remote-helper
Running
Systemd unit files are provided for the node under the /systemd folder.
They can be used as a starting point for further customization.
For running in debug mode, see HACKING.md.
Feedback
If you have feedback, feel free to create issues using rad issue, join
our Zulip, or email feedback@radicle.dev.
Emails sent to this address are automatically posted to
our public #feedback channel on Zulip, revealing the
From header (which usually contains your name and email
address). This allows us to discuss your feedback on Zulip, and, if necessary,
respond to you via email.
Contributing
See CONTRIBUTING.md and HACKING.md for an introduction to contributing to Radicle.
Packages
Community members maintain packages for various package managers. This makes it a lot easier to install Radicle and allows tighter integration of Radicle with various distributions. Thanks!
APT (Debian, etc.)
See https://radicle.dev/apt/ and rad:z2nDKoCF4hg6xVrv7v93LmWHDJKUr maintained by Lars Wirzenius and Richard Levitte
Arch
See archlinux.org/packages and gitlab.archlinux.org maintained by tippfehlr and kpcyrd.
NixOS
See search.nixos.org/packages and search.nixos.org/options maintained by @NixOS/radicle.
Also see home-manager-options.extranix.com for usage with home-manager.
License
Radicle is distributed under the terms of both the MIT license and the Apache License (Version 2.0).
See LICENSE-APACHE and LICENSE-MIT for details.