358324883c
Currently, if refs are updated while the node is stopped, these refs are not immediately announced when the node starts, due to the node being unaware of the updates. To remedy this, on startup, we compare the refs we have in storage with the refs we announced to the network. Since only our own refs could have changed while the node was stopped, this change only applies to owned refs. If we detect that storage has changed while the node was stopped, we create ref announcements for the updated repos and store them in our gossip database. These announcements will be included with other historical gossip announcements when nodes connect to us. To keep track of what was announced, we store our local node's sync status in the database. This is also useful when using the `rad sync status` command, as it tells us what oid our local node is at, and whether it is aware of our local changes yet. In addition to this, we make a small fix: previously, inventory and ref announcements originating from our local node were not stored in the announcement database. We ensure that they are via the new `announce` method. |
||
|---|---|---|
| .github/workflows | ||
| .nix | ||
| debian | ||
| radicle | ||
| radicle-cli | ||
| radicle-cli-test | ||
| radicle-cob | ||
| radicle-crdt | ||
| radicle-crypto | ||
| radicle-dag | ||
| radicle-fetch | ||
| radicle-httpd | ||
| radicle-node | ||
| radicle-remote-helper | ||
| radicle-ssh | ||
| radicle-term | ||
| radicle-tools | ||
| scripts | ||
| systemd | ||
| .dockerignore | ||
| .env.seed | ||
| .gitignore | ||
| .gitsigners | ||
| ARCHITECTURE.md | ||
| CONTRIBUTING.md | ||
| Cargo.lock | ||
| Cargo.toml | ||
| DCO | ||
| HACKING.md | ||
| LICENSE-APACHE | ||
| LICENSE-MIT | ||
| README.md | ||
| build.rs | ||
| deny.toml | ||
| docker-compose.yml | ||
| git-remote-rad.1.adoc | ||
| rad-patch.1.adoc | ||
| rad.1.adoc | ||
| radicle-httpd.1.adoc | ||
| radicle-node.1.adoc | ||
| rust-toolchain | ||
README.md
❤️🪵
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 implemention 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.
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:
sh <(curl -sSf https://radicle.xyz/install)
📦 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 radicle-cli --force --locked
cargo install --path radicle-node --force --locked
cargo install --path radicle-remote-helper --force --locked
Or directly from our seed node:
cargo install --force --locked --git https://seed.radicle.xyz/z3gqcJUoA1n9HaHKufZs5FCSGazv5.git \
radicle-cli radicle-node radicle-remote-helper
Running
Systemd unit files are provided for the node and HTTP daemon under the
/systemd folder. They can be used as a starting point for further
customization.
Additionally, a Dockerfile is included under both crates.
For running in debug mode, see HACKING.md.
Contributing
See CONTRIBUTING.md and HACKING.md for an introduction to contributing to Radicle.
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.