Add Lightning Terminal fragment

[dennisreimann]

Closes btcpayserver/btcpayserver#2706.

How to test

Go to your BTCPay Server directory and run the following commands:

# Checkout this pull request
git remote add dennisreimann https://github.com/dennisreimann/btcpayserver-docker.git
git fetch dennisreimann
git checkout -b dennisreimann/lit
git pull dennisreimann lit

# Prepare
export BTCPAYGEN_ADDITIONAL_FRAGMENTS="$BTCPAYGEN_ADDITIONAL_FRAGMENTS;opt-add-lightning-terminal"
export LIT_PASSWD="aSecretPasswordLikeRockstar"

# Install
. ./btcpay-setup.sh -i

# Check
docker logs generated_lnd_lit_1

The log should give you an output like this:

2021-11-03 07:42:05.976 [INF] LITD: Dialing lnd gRPC server at lnd_bitcoin:10009
2021-11-03 07:42:06.072 [INF] LITD: Listening for http_tls on: 127.0.0.1:8443
2021-11-03 07:42:06.073 [INF] LITD: Listening for http on: [::]:8080
----------------------------------------------------------
 Lightning Terminal (LiT) by Lightning Labs               
                                                          
 Operating mode      remote                                   
 Node status         online                                   
 Alias               My BTCPay Server                                 
 Version             0.13.3-beta commit=basedon-v0.13.3-beta-fresh-btcpay                                   
 Web interface       127.0.0.1:8443, 0.0.0.0:8080 (open https://127.0.0.1:8443 or http://localhost:8080 in your browser)         
----------------------------------------------------------
2021-11-03 07:42:06.381 [INF] LNDC: Creating lnd connection to lnd_bitcoin:10009
2021-11-03 07:42:06.382 [INF] LNDC: Connected to lnd

1. Go to your BTCPay Server backend and see the Server Settings > Services:
2. You should see "Lightning Terminal" under the "Other external services".
3. Open LiT by clicking the "See information" link on the right side.
4. Log in using the password chosen in the setup (see bash commands) and see if everything works as expected.

[dennisreimann]

@astupidmoose can you help testing this?

[astupidmoose]

I'll see what I can do. I don't think I have any test instances running but if I get some time I can try in the next few days.

[dennisreimann]

I've added instructions on how to test this PR, let me know in case I can be of more help.

[astupidmoose]

Setup and install worked. Gonna play around with Loop and Pool in a bit, but that would be an issue with Lightning Terminal if anything. This docker seems to be working good.

One thing I noticed was my logs were a bit different:

2021-11-18 18:32:54.381 [INF] LITD: Listening for http on: [::]:8080
----------------------------------------------------------
 Lightning Terminal (LiT) by Lightning Labs

 Operating mode      remote
 Node status         locked
 Alias               ???? (node is locked)
 Version             ???? (node is locked)
 Web interface       127.0.0.1:8443, 0.0.0.0:8080 (open https://127.0.0.1:8443 or http://localhost:8080 in your browser)
----------------------------------------------------------
2021-11-18 18:32:54.649 [INF] LNDC: Creating lnd connection to lnd_bitcoin:10009
2021-11-18 18:32:54.650 [INF] LNDC: Connected to lnd

Not sure why I have "locked", but this node is an XXS pruned node, so maybe the issue?

[dennisreimann]

@guggero Du you know why it says node is locked in that case?

[guggero]

I don't know, is the wallet still locked maybe? Hard to say without seeing more of the log.

[NicolasDorier]

you need to save LIT_PASSWD in BTCPAY_ENV_FILE. Check in helpers.sh.
Else it won't be saved, the next time you connect you connect to btcpay ssh and btcpay-up.sh, it will be removed.

[NicolasDorier]

Is there a way to avoid the LIT_PASSWD completely? What if it is empty, what happen?
Also need doc in the README.md, we list all fragments there.

[dennisreimann]

Is there a way to avoid the LIT_PASSWD completely? What if it is empty, what happen?

It will refuse to start: could not load config: could not read UI password: mandatory password for UI not configured.

Also need doc in the README.md, we list all fragments there.

Rebased and added. 👍

[dennisreimann]

@NicolasDorier Are there still any objections? I'd upgrade it to the just released v0.6.0-alpha and we can merge it then?