1e8f5b2259
To determine the correct Namespaces to use, the repo Policy and Scope are consulted. If the policy is Block then this is a failure state and is reported to the other end. Otherwise, if the policy is Track, then the scope is checked. For the Trusted Scope then the Namespaces should consist of all tracked nodes and delegates for the given repository. However, the repository might not exist and so it is necessary for the whole repository to be fetched. For the All Scope, all Namespaces are fetched. Signed-off-by: Fintan Halpenny <fintan.halpenny@gmail.com> X-Clacks-Overhead: GNU Terry Pratchett |
||
|---|---|---|
| .github/workflows | ||
| .nix | ||
| radicle | ||
| radicle-cli | ||
| radicle-cli-test | ||
| radicle-cob | ||
| radicle-crdt | ||
| radicle-crypto | ||
| radicle-dag | ||
| radicle-httpd | ||
| radicle-node | ||
| radicle-remote-helper | ||
| radicle-ssh | ||
| radicle-term | ||
| radicle-tools | ||
| .dockerignore | ||
| .env.seed | ||
| .gitignore | ||
| CONTRIBUTING.md | ||
| Cargo.lock | ||
| Cargo.toml | ||
| DCO | ||
| LICENSE-APACHE | ||
| LICENSE-MIT | ||
| README.md | ||
| build.rs | ||
| docker-compose.yml | ||
| rust-toolchain | ||
README.md
❤️🪵
Radicle Heartwood Protocol & Stack
Heartwood is in the early development phase and is not yet ready for use.
Installation
# Command line tools
$ cargo install --locked --path ./radicle-cli
# The radicle node
$ cargo install --locked --path ./radicle-node
# Git tool to support the 'rad://' remote scheme
$ cargo install --locked --path ./radicle-remote-helper