88 lines
4.5 KiB
Markdown
88 lines
4.5 KiB
Markdown
The `rad sync` command announces changes to the network and waits for other
|
|
nodes to be synchronized with those changes.
|
|
|
|
For instance let's create an issue and sync it with the network:
|
|
|
|
```
|
|
$ rad issue open --title "Test `rad sync`" --description "Check that the command works" -q --no-announce
|
|
```
|
|
|
|
If we check the sync status, we see that our peers are out of sync:
|
|
Our own node is also out of sync, since we used `--no-announce`.
|
|
It isn't aware of the updates to the repo.
|
|
|
|
```
|
|
$ rad sync status --sort-by alias
|
|
╭──────────────────────────────────────────────────────────────────────────────────────────╮
|
|
│ ● NID Alias Address Status At Timestamp │
|
|
├──────────────────────────────────────────────────────────────────────────────────────────┤
|
|
│ ● z6MknSL…StBU8Vi alice alice.radicle.xyz:8776 out-of-sync f209c9f [ ... ] │
|
|
│ ● z6Mkt67…v4N1tRk bob bob.radicle.xyz:8776 out-of-sync f209c9f [ ... ] │
|
|
│ ● z6Mkux1…nVhib7Z eve eve.radicle.xyz:8776 out-of-sync f209c9f [ ... ] │
|
|
╰──────────────────────────────────────────────────────────────────────────────────────────╯
|
|
```
|
|
|
|
Now let's run `rad sync`. This will announce the issue refs to the network and
|
|
wait for nodes to announce that they have fetched those refs.
|
|
|
|
```
|
|
$ rad sync --announce
|
|
✓ Synced with 2 node(s)
|
|
```
|
|
|
|
If we try to sync again after the nodes have synced, we will already
|
|
be up to date.
|
|
|
|
```
|
|
$ rad sync --announce
|
|
✓ Nothing to announce, already in sync with network (see `rad sync status`)
|
|
```
|
|
|
|
We can also use the `--fetch` option to only fetch objects:
|
|
|
|
```
|
|
$ rad sync --fetch
|
|
✓ Fetching rad:z42hL2jL4XNk6K8oHQaSWfMgCL7ji from z6Mkt67…v4N1tRk..
|
|
✓ Fetching rad:z42hL2jL4XNk6K8oHQaSWfMgCL7ji from z6Mkux1…nVhib7Z..
|
|
✓ Fetched repository from 2 seed(s)
|
|
```
|
|
|
|
Specifying both `--fetch` and `--announce` is equivalent to specifying none:
|
|
|
|
```
|
|
$ rad sync --fetch --announce
|
|
✓ Fetching rad:z42hL2jL4XNk6K8oHQaSWfMgCL7ji from z6Mkt67…v4N1tRk..
|
|
✓ Fetching rad:z42hL2jL4XNk6K8oHQaSWfMgCL7ji from z6Mkux1…nVhib7Z..
|
|
✓ Fetched repository from 2 seed(s)
|
|
✓ Nothing to announce, already in sync with network (see `rad sync status`)
|
|
```
|
|
|
|
It's also possible to use the `--seed` flag to only sync with a specific node:
|
|
|
|
```
|
|
$ rad sync --fetch --seed z6Mkt67GdsW7715MEfRuP4pSZxJRJh6kj6Y48WRqVv4N1tRk
|
|
✓ Fetching rad:z42hL2jL4XNk6K8oHQaSWfMgCL7ji from z6Mkt67…v4N1tRk..
|
|
✓ Fetched repository from 1 seed(s)
|
|
```
|
|
|
|
And the `--replicas` flag to sync with a number of nodes:
|
|
|
|
```
|
|
$ rad sync --fetch --replicas 1
|
|
✓ Fetching rad:z42hL2jL4XNk6K8oHQaSWfMgCL7ji from z6Mkt67…v4N1tRk..
|
|
✓ Fetched repository from 1 seed(s)
|
|
```
|
|
|
|
We can check the sync status again to make sure everything's in sync:
|
|
|
|
```
|
|
$ rad sync status --sort-by alias
|
|
╭─────────────────────────────────────────────────────────────────────────────────────╮
|
|
│ ● NID Alias Address Status At Timestamp │
|
|
├─────────────────────────────────────────────────────────────────────────────────────┤
|
|
│ ● z6MknSL…StBU8Vi alice alice.radicle.xyz:8776 synced 9f615f9 [ ... ] │
|
|
│ ● z6Mkt67…v4N1tRk bob bob.radicle.xyz:8776 synced 9f615f9 [ ... ] │
|
|
│ ● z6Mkux1…nVhib7Z eve eve.radicle.xyz:8776 synced 9f615f9 [ ... ] │
|
|
╰─────────────────────────────────────────────────────────────────────────────────────╯
|
|
```
|