You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Perform submarine swaps via the [Lightning Loop](https://lightning.engineering/loop) service
13
+
- Perform submarine swaps via
14
+
the [Lightning Loop](https://lightning.engineering/loop) service
12
15
- Classify channels according to your node's operating mode
13
-
- Run a single binary that integrates [`loopd`](https://github.com/lightninglabs/loop),
16
+
- Run a single binary that integrates
17
+
[`loopd`](https://github.com/lightninglabs/loop),
14
18
[`poold`](https://github.com/lightninglabs/pool) and
15
19
[`faraday`](https://github.com/lightninglabs/faraday) daemons all in one
16
20
- Access a preview release of the Pool UI
17
21
- Use Pool to earn sats by opening channels to those needing inbound liquidity
18
22
19
23
## Installation
20
-
Download the latest binaries from the [releases](https://github.com/lightninglabs/lightning-terminal/releases) page.
21
24
22
-
Additionally, you can find detailed instructions on the [docs.lightning.engineering](https://docs.lightning.engineering/lightning-network-tools/lightning-terminal/get-lit) page.
25
+
Download the latest binaries from the [releases](https://github.com/lightninglabs/lightning-terminal/releases)
26
+
page.
27
+
28
+
Additionally, you can find detailed instructions on the [docs.lightning.engineering](https://docs.lightning.engineering/lightning-network-tools/lightning-terminal/get-lit)
29
+
page.
23
30
24
31
## Execution
32
+
25
33
Run Lightning Terminal with a local `lnd` instance:
26
34
27
35
```shell
@@ -30,39 +38,71 @@ Run Lightning Terminal with a local `lnd` instance:
30
38
31
39
Visit https://localhost:8443 to access Terminal.
32
40
33
-
Note that a password with a minimum of 8 characters is required to run Lightning Terminal. In a production environment, it's recommended that you store this password as an environment variable to avoid it being recorded in the command history.
41
+
Note that a password with a minimum of 8 characters is required to run Lightning
42
+
Terminal. In a production environment, it's recommended that you store this
43
+
password as an environment variable to avoid it being recorded in the command
44
+
history.
34
45
35
-
To use LiT with a remote `lnd` instance please [follow these instructions](./docs/config-lnd-remote.md). If you would like to replace your existing LND instance with the one integrated within LiT please see [configuring Terminal](./docs/config-lnd-integrated.md).
46
+
To use LiT with a remote `lnd` instance
47
+
please [follow these instructions](./docs/config-lnd-remote.md). If you would
48
+
like to replace your existing LND instance with the one integrated within LiT
49
+
please see [configuring Terminal](./docs/config-lnd-integrated.md).
36
50
37
51
## LND
38
-
Note that LiT requires `lnd` to be built with **all of its subservers** and requires running at least v0.11.0. Download the latest [official release binary](https://github.com/lightningnetwork/lnd/releases/latest) or build `lnd` from source by following the [installation instructions](https://github.com/lightningnetwork/lnd/blob/master/docs/INSTALL.md). If you choose to build `lnd` from source, use the following command to enable all the relevant subservers:
52
+
53
+
Note that LiT requires `lnd` to be built with **all of its subservers** and
the [installation instructions](https://github.com/lightningnetwork/lnd/blob/master/docs/INSTALL.md).
58
+
If you choose to build `lnd` from source, use the following command to enable
59
+
all the relevant subservers:
39
60
40
61
```shell
41
62
⛰ make install tags="signrpc walletrpc chainrpc invoicesrpc"
42
63
```
43
64
44
65
## Interaction
45
-
If you plan to run LiT on a remote machine but access the web-interface from your computer you may not want to deal with self-signed certificate browser warnings. To avoid these warnings configure the HTTP server to use a certificate from [Let's Encrypt](https://letsencrypt.org/). View the
46
-
[Let's Encrypt Configuration](./docs/letsencrypt.md) doc for instructions on how to configure this.
66
+
67
+
If you plan to run LiT on a remote machine but access the web-interface from
68
+
your computer you may not want to deal with self-signed certificate browser
69
+
warnings. To avoid these warnings configure the HTTP server to use a certificate
70
+
from [Let's Encrypt](https://letsencrypt.org/). View the
71
+
[Let's Encrypt Configuration](./docs/letsencrypt.md) doc for instructions on how
72
+
to configure this.
47
73
48
74
## Upgrading
49
-
If you used command line arguments with previous versions then you don't need to change anything when upgrading.
50
75
51
-
To upgrade from v0.1.1-alpha or earlier simply create a `lit.conf` file in your LiT directory. The default location LiT uses depends on your operating system:
76
+
If you used command line arguments with previous versions then you don't need to
77
+
change anything when upgrading.
78
+
79
+
To upgrade from v0.1.1-alpha or earlier simply create a `lit.conf` file in your
80
+
LiT directory. The default location LiT uses depends on your operating system:
Move all the configuration settings specific to LiT from `lnd.conf` to `lit.conf` and remove any previous LiT-specific customizations from the configuration settings in `lnd.conf`. Note that any section headers (`[ Example ]`) in `lit.conf` should be removed or changed to comments (`# Example`).
86
+
Move all the configuration settings specific to LiT from `lnd.conf` to
87
+
`lit.conf` and remove any previous LiT-specific customizations from the
88
+
configuration settings in `lnd.conf`. Note that any section headers (
89
+
`[ Example ]`) in `lit.conf` should be removed or changed to comments (
90
+
`# Example`).
57
91
58
92
## Usage
59
-
Read the [walkthrough](docs/WALKTHROUGH.md) document to learn more about how to use LiT.
93
+
94
+
Read the [walkthrough](docs/WALKTHROUGH.md) document to learn more about how to
95
+
use LiT.
60
96
61
97
## Troubleshooting
62
-
If you encounter any issues please see our [troubleshooting guide](./docs/troubleshooting.md).
0 commit comments