Skip to content

Commit 3769fc2

Browse files
Leo Weesegitbook-bot
Leo Weese
authored andcommitted
GITBOOK-471: change request with no subject merged in GitBook
1 parent 9b6a2b9 commit 3769fc2

File tree

1 file changed

+15
-23
lines changed

1 file changed

+15
-23
lines changed

Diff for: lightning-network-tools/loop/get-started.md

+15-23
Original file line numberDiff line numberDiff line change
@@ -1,39 +1,31 @@
11
---
2-
description: Install and run Loop
2+
description: Install Loopd from source or the binaries
33
---
44

5-
# 🛠 Get Started
5+
# 🛠 Get Started
66

77
## Install Loop <a href="#docs-internal-guid-a15d1019-7fff-cd65-8961-f4145a3bd0d5" id="docs-internal-guid-a15d1019-7fff-cd65-8961-f4145a3bd0d5"></a>
88

9-
Loop comes bundled with [Lightning Terminal](../lightning-terminal/). Meaning, if you have Lightning Terminal installed, you can already access Loop through the command line and you may skip the step below.
9+
Loop comes bundled with [Lightning Terminal](../lightning-terminal/) (`litd`). If you are already running `litd`, you can access Loop through the command line or the [Lightning Terminal UI](../lightning-terminal/connect.md) and may skip the steps below.
1010

11-
\[[Follow this guide to install Lightning Terminal](../lightning-terminal/get-lit.md)]
11+
[Follow this guide to install Lightning Terminal](../lightning-terminal/get-lit.md)
1212

13-
To run Loop you need to be running LND from the [binary releases](https://github.com/lightningnetwork/lnd/releases), or compile from source with the command `make install tags="signrpc walletrpc chainrpc invoicesrpc"`
13+
## Installation
1414

15-
You can run Loop directly from the binary releases, or compile it from source:
15+
To run Loop you need to be running LND from the[ binary releases](https://github.com/lightningnetwork/lnd/releases), or compile from source with the command make install `tags="signrpc walletrpc chainrpc invoicesrpc"`
1616

17-
`git clone https://github.com/lightninglabs/loop.git`\
18-
`cd loop`\
19-
`make && make install`
20-
21-
## Run Loop
22-
23-
Loop, like bitcoind, LND and others, comes with two components: Loopd and a command line interface (CLI) to interact with it called loop.
17+
### Run the Binary <a href="#docs-internal-guid-42583cca-7fff-ed7e-46c6-2304f786c1e8" id="docs-internal-guid-42583cca-7fff-ed7e-46c6-2304f786c1e8"></a>
2418

25-
You will need to first run Loop with the command `loopd`
19+
You can run Loop directly from the binary releases, [which you can find here](https://github.com/lightninglabs/loop/releases).
2620

27-
If you want to run Loop in the background, you can also write the output to `/dev/null` by amending `&>/dev/null &` to the above command.
21+
### Compile from source
2822

29-
### Lightning Terminal
23+
You can compile Loop from source. This requires Golang. Instructions for how to install Go can be found in the [LND installation guide](../lnd/run-lnd.md).
3024

31-
If you are running Lightning Terminal already, either locally or remotely, Loop will be running inside of it already. You can make use of Loop using the Lightning Terminal GUI as explained in the Guide to Lightning Terminal.
32-
33-
If you want to interact with Loop in Lightning Terminal through the command line, you will need to specify the port and tls.cert every time you run loop using the flag `--rpcserver=localhost:8443 --tlscertpath=~/.lit/tls.cert`, for example `./loop --rpcserver=localhost:8443 --tlscertpath=~/.lit/tls.certquote in 500000`
34-
35-
Alternatively you may also copy over the `tls.cert` from `~/.lit` into `~/.loop/mainnet`
25+
`git clone https://github.com/lightninglabs/loop.git`\
26+
`cd loop`\
27+
`make && make install`
3628

37-
If you are a Lightning Terminal user and want to avoid having to include the `--rpcserver` command every time or navigate to the location of the loop binary, you may also add an entry to your aliases file (e.g. `~/.bash_aliases`):
29+
## Configuration
3830

39-
`alias loop=’~/path/to/loop --rpcserver=localhost:8443’`
31+
By default, the `loopd.conf` is placed in `~/.loop/mainnet/` If you are starting `loopd` on another network (e.g. `loopd --network=signet`), the configuration file is expected in the relevant directory (e.g. `~/.loop/signet`). You may also pass a custom directory with the `--configfile=` flag.

0 commit comments

Comments
 (0)