43 lines
8.7 KiB
Markdown
43 lines
8.7 KiB
Markdown
● Done. Here's how to use it:
|
|
|
|
Setup (two machines or locations)
|
|
|
|
Machine A (e.g., your main dev machine):
|
|
# 1. Start the bridge
|
|
uv run radicle-rns bridge
|
|
|
|
# Note the RNS hash printed, e.g.: abc123def456...
|
|
|
|
# 2. Configure radicle-node to use the bridge
|
|
# Edit ~/.radicle/node/config.toml:
|
|
[[seeds]]
|
|
address = "127.0.0.1:8777"
|
|
|
|
# 3. Start radicle-node normally
|
|
rad node start
|
|
|
|
Machine B (remote location, connected via LoRa/mesh):
|
|
# 1. Start bridge and connect to Machine A
|
|
uv run radicle-rns bridge --connect <machine-a-hash>
|
|
|
|
# 2. Same radicle config
|
|
# Edit ~/.radicle/node/config.toml:
|
|
[[seeds]]
|
|
address = "127.0.0.1:8777"
|
|
|
|
# 3. Start radicle-node
|
|
rad node start
|
|
|
|
Now use Radicle normally:
|
|
# On either machine
|
|
rad clone rad:z3xyz...
|
|
rad push
|
|
rad pull
|
|
rad issue list
|
|
rad patch list
|
|
|
|
The bridges tunnel all Radicle traffic over Reticulum automatically.
|
|
|
|
---
|
|
Do you have radicle-node installed to test? If not I can help set it up, or we can test the bridge layer first with just the RNS transport.
|