Federated via graft
Actualiser README.md
author
mallory
date
(Sep 13, 2026, 12:14 PM UTC)
commit
26a42921
26a42921d6029b04a9d06607c5787af43a4edcdc
parent
8d237021
8d2370214b7ad5a546e45c8c7298adb84982524a
+1
-1
+1
-1
README.md
+1
-1
README.md
···
14
14
- Now, Alice and Bob can work on the same repo but on two different forge instances
15
15
- Question: does having a simple **sync/remote** button solve the collaboration between instances?
16
16
17
-
## Solving Alice & Bob's use case with [https://f1.cyberwild.org/forgeadmin/graft](graft)
17
+
## Solving Alice & Bob's use case with (graft)[https://f1.cyberwild.org/forgeadmin/graft]
18
18
19
19
1. One graft instance runs somewhere and already mirrors `federation-x` — say it started as Alice's own repo on f1, paired with a Radicle repo.
20
20
2. To bring Bob's f2 in: Bob generates a token on his own instance (scoped `write:repository` + `write:issue`), sends it to whoever runs graft — ideally through graft's own `/share/new` one-time link rather than chat. The graft admin opens `/add-peer`, picks the `federation-x` series from the dropdown, fills in f2's base URL/owner/repo and Bob's token, confirms with the admin password. The Radicle side (RID, node, explorer) is inherited from the series automatically — nobody enters it by hand.