Skip to content

Commit

Permalink
use consistent hostnames
Browse files Browse the repository at this point in the history
  • Loading branch information
ferd committed Jul 15, 2024
1 parent 34d96db commit 816af8f
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions USAGE.md
Original file line number Diff line number Diff line change
Expand Up @@ -246,7 +246,7 @@ This shows the node is running, and the host name generated is `[email protected]
We can validate the configuration seen by the host in its internal format:

```
./_build/prod/bin/revault_cli list -node [email protected]
./_build/prod/bin/revault_cli list
Config parsed from /home/ferd/.config/ReVault/config.toml:
#{<<"backend">> => #{<<"mode">> => <<"disk">>},
<<"db">> => #{<<"path">> => <<"/home/ferd/revault-docs/revault/db/">>},
Expand All @@ -270,7 +270,7 @@ Everything seems alright, and you can see that by default the app ignores the `.
Let's scan the files:

```
$ ./_build/prod/bin/revault_cli scan -node [email protected]
$ ./_build/prod/bin/revault_cli scan
Scanning music: {badrpc,
{'EXIT',
{noproc,
Expand Down Expand Up @@ -365,9 +365,9 @@ The problem, of course, is that our initial node does not accept connections. Le
This explicitly allows the `beta` certificate to synchronize the music directory. Restart the initial node and retry seeding. It should look like the following:

```
$ ./_build/prod/bin/revault_cli remote-seed -dirs music -node beta@vps.ferd.site -peer alpha
$ ./_build/prod/bin/revault_cli remote-seed -dirs music -node beta@ferd.local -peer alpha
Seeding music from alpha: ok
$ ./_build/prod/bin/revault_cli scan -dirs music -node beta@vps.ferd.site
$ ./_build/prod/bin/revault_cli scan -dirs music -node beta@ferd.local
Scanning music: ok
```

Expand All @@ -382,7 +382,7 @@ The previous procedure works well when the new node can connect to the old node
This is a common pattern when you initialize the first node on your own computer, and want to synchronize with a new remote server that won't be able to connect to your home network. The `seed` command is useful for this:

```
λ [vps] ReVault → main* → ./_build/prod/bin/revault_cli seed --help
$ ./_build/prod/bin/revault_cli seed --help
usage: revault-cli seed [-node <node>] [-path <path>] [-dirs <dirs>...]
Optional arguments:
Expand Down Expand Up @@ -420,7 +420,7 @@ Assuming your hosts are all set up fine according to prior instructions, you can
```
$ ls /tmp/revault-docs/music_beta/
$ ./_build/prod/bin/revault_cli sync -dirs music -node beta@vps.ferd.site -peer alpha
$ ./_build/prod/bin/revault_cli sync -dirs music -node beta@ferd.local -peer alpha
Scanning music: ok
Syncing music with alpha: ok
$ ls /tmp/revault-docs/music_beta/
Expand Down

0 comments on commit 816af8f

Please sign in to comment.