Skip to content

fix: export DEFRA_KEYRING_SECRET #196

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
akc2267 wants to merge 1 commit into
base: master
Choose a base branch
from
Open

fix: export DEFRA_KEYRING_SECRET #196

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions defradb_versioned_docs/version-0.19.0/getting-started.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ If a `.env` file is available in the working directory, the secret can be stored
Keys will be randomly generated on the initial start of the node if they are not found. To generate keys:

```bash
DEFRA_KEYRING_SECRET=<make_a_password>
export DEFRA_KEYRING_SECRET=<make_a_password>
defradb keyring generate
```

Expand Down Expand Up @@ -329,7 +329,7 @@ Let's go through an example of two nodes (*nodeA* and *nodeB*) connecting with e
In the first terminal, start *nodeA* with a default configuration:

```bash
DEFRA_KEYRING_SECRET=<make_a_password>
export DEFRA_KEYRING_SECRET=<make_a_password>
defradb start
```

Expand All @@ -343,7 +343,7 @@ echo $PEER_ID
In this second terminal, start *nodeB*, configured to connect with *nodeA*:

```bash
DEFRA_KEYRING_SECRET=<make_a_password_for_node_B>
export DEFRA_KEYRING_SECRET=<make_a_password_for_node_B>
defradb start --rootdir ~/.defradb-nodeB --url localhost:9182 --p2paddr /ip4/127.0.0.1/tcp/9172 --peers /ip4/127.0.0.1/tcp/9171/p2p/$PEER_ID
```

Expand Down
6 changes: 3 additions & 3 deletions docs/defradb/getting-started.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ If a `.env` file is available in the working directory, the secret can be stored
Keys will be randomly generated on the initial start of the node if they are not found. To generate keys:

```bash
DEFRA_KEYRING_SECRET=<make_a_password>
export DEFRA_KEYRING_SECRET=<make_a_password>
defradb keyring generate
```

Expand Down Expand Up @@ -329,7 +329,7 @@ Let's go through an example of two nodes (*nodeA* and *nodeB*) connecting with e
In the first terminal, start *nodeA* with a default configuration:

```bash
DEFRA_KEYRING_SECRET=<make_a_password>
export DEFRA_KEYRING_SECRET=<make_a_password>
defradb start
```

Expand All @@ -343,7 +343,7 @@ echo $PEER_ID
In this second terminal, start *nodeB*, configured to connect with *nodeA*:

```bash
DEFRA_KEYRING_SECRET=<make_a_password_for_node_B>
export DEFRA_KEYRING_SECRET=<make_a_password_for_node_B>
defradb start --rootdir ~/.defradb-nodeB --url localhost:9182 --p2paddr /ip4/127.0.0.1/tcp/9172 --peers /ip4/127.0.0.1/tcp/9171/p2p/$PEER_ID
```

Expand Down