mirror of
https://seed.radicle.dev/rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5.git
synced 2026-11-21 18:40:39 +08:00
This makes the default policy `block` with scope `all`. The good thing about this is that you don't have to manage individual nodes in the beginning. You simply seed the repos you want, and everything is followed within those repos. This matches user expectations, as `rad seed` does what you expect it to do. For open-policy seed nodes, it also means that simply changing `block` to `allow` from the default config is all you need. This leaves the non-default `followed` scope as a more "advanced" setting, since it is much more cumbersome: it forces you to follow a user before you can see their issues/patches, which is not something most users expect coming from old-shcool forges.
1.6 KiB
1.6 KiB
When using an open seeding policy, it can be useful to block individual repositories from being seeded.
For instance, if our default policy is to seed, any unknown repository will have its policy set to allow seeding:
$ rad inspect rad:z42hL2jL4XNk6K8oHQaSWfMgCL7ji --policy
Repository rad:z42hL2jL4XNk6K8oHQaSWfMgCL7ji is being seeded with scope `all`
Since there is no policy specific to this repository, there's nothing to be removed.
$ rad seed
No seeding policies to show.
But if we wanted to prevent this repository from being seeded, while
allowing all other repositories, we could use rad block:
$ rad block rad:z42hL2jL4XNk6K8oHQaSWfMgCL7ji
✓ Policy for rad:z42hL2jL4XNk6K8oHQaSWfMgCL7ji set to 'block'
We can see that it is now no longer seeded:
$ rad inspect rad:z42hL2jL4XNk6K8oHQaSWfMgCL7ji --policy
Repository rad:z42hL2jL4XNk6K8oHQaSWfMgCL7ji is not being seeded
And a 'block' policy was added:
$ rad seed
╭───────────────────────────────────────────────────────╮
│ RID Scope Policy │
├───────────────────────────────────────────────────────┤
│ rad:z42hL2jL4XNk6K8oHQaSWfMgCL7ji followed block │
╰───────────────────────────────────────────────────────╯