flywithu/Learning-Bitcoin-from-the-Command-Line
1
1
Fork 0
mirror of https://github.com/ChristopherA/Learning-Bitcoin-from-the-Command-Line.git synced 2025-06-07 07:56:31 +00:00
Code Issues Releases Wiki Activity

Now grab the USER and PASS just before using them

Browse Source
This commit is contained in:
Shannon Appelcline 2021-01-05 09:17:30 -10:00 committed by GitHub
parent d28c5a6db0
commit 6097d8e11a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 12 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
18_2__Interlude_Accessing_a_Second_Lightning_Node.md
View File

@ -111,15 +111,7 @@ $ sudo cp $GOPATH/bin/lnd $GOPATH/bin/lncli /usr/bin
Unlike with c-lightning, you will need to create a default config file for LND. Unlike with c-lightning, you will need to create a default config file for LND.
First, you need to retrieve your rpcuser and rpcpassword. Here's an automated way to do so: However first, you need to enable ZMQ on your Bitcoind, if you didn't already in [§15.3](15_3_Receiving_Bitcoind_Notifications_with_C.md).
```
$ BITCOINRPC_USER=$(cat ~standup/.bitcoin/bitcoin.conf | grep rpcuser | awk -F = '{print $2}')
$ BITCOINRPC_PASS=$(cat ~standup/.bitcoin/bitcoin.conf | grep rpcpassword | awk -F = '{print $2}')
```
> :warning: **WARNING:** Obviously, never store your RPC password in a shell variable in a production environment.
Second, you need to enable ZMQ on your Bitcoind, if you didn't already in [§15.3](15_3_Receiving_Bitcoind_Notifications_with_C.md).
This requires adding the following to your `~/.bitcoin/bitcoin.conf` file if it's not already there: This requires adding the following to your `~/.bitcoin/bitcoin.conf` file if it's not already there:
``` ```
@ -144,7 +136,17 @@ $ bitcoin-cli getzmqnotifications
} }
] ]
``` ```
Now you're ready to create a config file: Now you're ready to create a config file.
First, you need to retrieve your rpcuser and rpcpassword. Here's an automated way to do so:
```
$ BITCOINRPC_USER=$(cat ~standup/.bitcoin/bitcoin.conf | grep rpcuser | awk -F = '{print $2}')
$ BITCOINRPC_PASS=$(cat ~standup/.bitcoin/bitcoin.conf | grep rpcpassword | awk -F = '{print $2}')
```
> :warning: **WARNING:** Obviously, never store your RPC password in a shell variable in a production environment.
Then, you can write the file:
``` ```
$ mkdir ~/.lnd $ mkdir ~/.lnd
$ cat > ~/.lnd/lnd.conf << EOF $ cat > ~/.lnd/lnd.conf << EOF