Repository navigation
Add Radicle Forge #88
Description
Activity
Hehe, this is interesting.
Of course they have own protocol and are self-hosted so you cannot access almost anything unless you use their protocol.
There are binaries on the download page, presumably including a CLI. https://radicle.dev/download
However, the sources are nowhere to be found, probably only available through the p2p network.
The documentation gives examples of nodes operated by the developers https://iris.radicle.network/ does not run the web UI nor does https://seed.radicle.dev/ but https://radicle.network/nodes/rosa.radicle.network/rad:z4V1sjrXqjvFdnCUbxPFqd5p4DtH5/tree/README.md does.
No trace of API docs I could find.
And github mirror https://github.com/radicle-dev/radicle-explorer
Presumably if you wanted a web API you would be talking to the explorer because it's the web component but the other tools (cli, tui, desktop) likely do not do that.
@m1karii can you help out by providing links to api documentation and existing cli clients for radicle?
Yes, the cli client is provided as part of the canonical implementation at heartwood. As for api - to my understanding there is none, since this project doesnt work like standard forge and is p2p instead
Of course they have own protocol and are self-hosted so you cannot access almost anything unless you use their protocol.
this is incorrect. radicle is built on top of git, it simply adds issues and patches (PRs) on top of code + the entire p2p thing... but the code is still available via git and direct downloads (curl)
@m1karii can you help out by providing links to api documentation and existing cli clients for radicle?
Yes, the cli client is provided as part of the canonical implementation at heartwood. As for api - to my understanding there is none, since this project doesnt work like standard forge and is p2p instead
That it's p2p does not prevent having HTTP API. So long as HTTP client exists (which is the explorer) it could. It does not seem to implement one, though. The heartwood rust-only code.
Of course they have own protocol and are self-hosted so you cannot access almost anything unless you use their protocol.
this is incorrect. radicle is built on top of git, it simply adds issues and patches (PRs) on top of code + the entire p2p thing... but the code is still available via git and direct downloads (curl)
The official web page has only binaries, no sources, and no link to the (unofficial) git mirror on github. So while getting the sources is possible without running radicle the official web page is not helpful in that.
The repository that implements the core protocol https://github.com/radicle-dev/heartwood has documentation for the CLI but does not seem to have documentation of the protocol details.
To facilitate using radicle repositories outside of the native tools you could probably do something like creating C exports for the protocol functions in heartwood, describe the so created API, and then other languages like go could possibly import those C API functions (although in the case of go importing C libraries seems rare, and NIH more common)
Radicle is next gen p2p forge / protocol. Within current political climate it is and will become increasingly important to have censorship resistant platforms available. Radicle is such platform for software development and therefore i consider it of great importance for this project to have interface for Radicle.