mirror of
https://seed.radicle.dev/rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5.git
synced 2026-11-16 00:00:37 +08:00
cloudhead
4605348d68
Split the commands and change the naming. * Tracking a repo is now called "seeding" * Tracking a peer is now called "following" In this commit, we don't change most of the internal code, only the user-facing part.
28 lines
1.0 KiB
Markdown
28 lines
1.0 KiB
Markdown
Using `rad clone` is useful if we want to create and fetch a project
|
|
that exists on Radicle, but perhaps we're in a scenario where we may
|
|
already have an existing Git repository and so a full clone is not
|
|
necessary.
|
|
|
|
Instead, we want to fetch the project from the network into our local
|
|
storage. In this scenario, we know that the project is
|
|
`rad:z42hL2jL4XNk6K8oHQaSWfMgCL7ji`. In order to fetch it, we first
|
|
have to update our seeding policy for the project.
|
|
|
|
```
|
|
$ rad seed rad:z42hL2jL4XNk6K8oHQaSWfMgCL7ji --no-fetch
|
|
✓ Seeding policy updated for rad:z42hL2jL4XNk6K8oHQaSWfMgCL7ji with scope 'all'
|
|
```
|
|
|
|
Now that the project is seeding we can fetch it and we will have it in
|
|
our local storage. Note that the `seed` command can also be told to fetch
|
|
by passing the `--fetch` option.
|
|
|
|
```
|
|
$ rad sync --fetch rad:z42hL2jL4XNk6K8oHQaSWfMgCL7ji
|
|
✓ Fetching rad:z42hL2jL4XNk6K8oHQaSWfMgCL7ji from z6MknSL…StBU8Vi..
|
|
✓ Fetched repository from 1 seed(s)
|
|
```
|
|
|
|
However, we don't have a local fork of the project. We can follow this
|
|
up with [rad-fork](rad-fork.md).
|