diff options
| author | Christopher Baines <mail@cbaines.net> | 2021-12-15 17:28:43 +0000 |
|---|---|---|
| committer | Christopher Baines <mail@cbaines.net> | 2021-12-15 17:28:43 +0000 |
| commit | fdc8b32f40bf6a5248bd6ced2fc7c615f12a4301 (patch) | |
| tree | ac40338ab46ba815c1acd9d6d988436cbab6ada9 | |
| parent | b75255a7bd61214f2695048991ba7da3422f3e6b (diff) | |
| download | nar-herder-fdc8b32f40bf6a5248bd6ced2fc7c615f12a4301.tar nar-herder-fdc8b32f40bf6a5248bd6ced2fc7c615f12a4301.tar.gz | |
Fix a couple of example commands
| -rw-r--r-- | README.org | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -85,7 +85,7 @@ nar-herder on foo.example.com will query storage.example.com to check if the nar-herder there is storing the files. #+BEGIN_SRC sh - nar-herder --storage=/var/lib/nars --storage-limit=0 --storage-nar-removal-criteria=stored-on=https://storage.example.com + nar-herder run-server --storage=/var/lib/nars --storage-limit=0 --storage-nar-removal-criteria=stored-on=https://storage.example.com #+END_SRC On the storage.example.com side, this is similar to the previous @@ -97,5 +97,5 @@ space. Like on foo.example.com, you can set a --storage-limit to prevent this. #+BEGIN_SRC sh - nar-herder --mirror=https://foo.example.com --storage=/var/lib/nars + nar-herder run-server --mirror=https://foo.example.com --storage=/var/lib/nars #+END_SRC |