config: add unix socket example to sample configuration
This commit is contained in:
parent
9f0e39f881
commit
8d6b49384a
@ -14,7 +14,7 @@
|
||||
|
||||
; Number of logfiles that the log rotation should keep. Setting it to 0 disables deletion of old log files.
|
||||
; maxlogfiles=3
|
||||
;
|
||||
;
|
||||
; Max log file size in MB before it is rotated.
|
||||
; maxlogfilesize=10
|
||||
|
||||
@ -29,7 +29,7 @@
|
||||
; the line below.
|
||||
; no-macaroons=true
|
||||
|
||||
; Path to write the admin macaroon for lnd's RPC and REST services if it
|
||||
; Path to write the admin macaroon for lnd's RPC and REST services if it
|
||||
; doesn't exist. This can be set if one wishes to store the admin macaroon in a
|
||||
; distinct location. By default, it is stored within lnd's main home directory.
|
||||
; Applications that are able to read this file, gains admin macaroon access
|
||||
@ -38,11 +38,11 @@
|
||||
; Path to write the read-only macaroon for lnd's RPC and REST services if it
|
||||
; doesn't exist. This can be set if one wishes to store the read-only macaroon
|
||||
; in a distinct location. The read only macaroon allows users which can read
|
||||
; the file to access RPC's which don't modify the state of the daemon.
|
||||
; the file to access RPCs which don't modify the state of the daemon.
|
||||
; readonlymacaroonpath=~/.lnd/readonly.macaroon
|
||||
|
||||
|
||||
; Specify the interfaces to listen on for p2p connections. One listen
|
||||
|
||||
; Specify the interfaces to listen on for p2p connections. One listen
|
||||
; address per line.
|
||||
; All ipv4 on port 9735:
|
||||
; listen=0.0.0.0:9735
|
||||
@ -50,25 +50,29 @@
|
||||
; listen=0.0.0.0:9735
|
||||
; listen=[::1]:9736
|
||||
|
||||
; Disable listening for incoming p2p connections. This will override all
|
||||
; Disable listening for incoming p2p connections. This will override all
|
||||
; listeners.
|
||||
; nolisten=1
|
||||
|
||||
; Specify the interfaces to listen on for gRPC connections. One listen
|
||||
; Specify the interfaces to listen on for gRPC connections. One listen
|
||||
; address per line.
|
||||
; Only ipv4 localhost on port 10009:
|
||||
; rpclisten=localhost:10009
|
||||
; On ipv4 localhost port 10009 and ipv6 port 10010:
|
||||
; rpclisten=localhost:10009
|
||||
; rpclisten=[::1]:10010
|
||||
; On an Unix socket:
|
||||
; rpclisten=unix:///var/run/lnd/lnd-rpclistener.sock
|
||||
|
||||
; Specify the interfaces to listen on for REST connections. One listen
|
||||
; Specify the interfaces to listen on for REST connections. One listen
|
||||
; address per line.
|
||||
; All ipv4 interfaces on port 8080:
|
||||
; restlisten=0.0.0.0:8080
|
||||
; On ipv4 localhost port 80 and 443:
|
||||
; restlisten=localhost:80
|
||||
; restlisten=localhost:443
|
||||
; On an Unix socket:
|
||||
; restlisten=unix:///var/run/lnd-restlistener.sock
|
||||
|
||||
|
||||
; Adding an external IP will advertise your node to the network. This signals
|
||||
@ -135,7 +139,7 @@ bitcoin.active=1
|
||||
|
||||
; Use Bitcoin's test network.
|
||||
; bitcoin.testnet=1
|
||||
;
|
||||
;
|
||||
; Use Bitcoin's simulation test network
|
||||
bitcoin.simnet=1
|
||||
|
||||
@ -146,7 +150,7 @@ bitcoin.simnet=1
|
||||
bitcoin.node=btcd
|
||||
|
||||
; Use the bitcoind back-end
|
||||
; bitcoin.node=bitcoind
|
||||
; bitcoin.node=bitcoind
|
||||
|
||||
; Use the neutrino (light client) back-end
|
||||
; bitcoin.node=neutrino
|
||||
@ -163,7 +167,7 @@ bitcoin.node=btcd
|
||||
; setting is assumed to be localhost with the default port for the current
|
||||
; network.
|
||||
; btcd.rpchost=localhost
|
||||
|
||||
|
||||
; Username for RPC connections to btcd. By default, lnd will attempt to
|
||||
; automatically obtain the credentials, so this likely won't need to be set
|
||||
; (other than for simnet mode).
|
||||
@ -181,7 +185,7 @@ bitcoin.node=btcd
|
||||
; The raw bytes of the daemon's PEM-encoded certificate chain which will be used
|
||||
; to authenticate the RPC connection. This only needs to be set if the btcd
|
||||
; node is on a remote host.
|
||||
; btcd.rawrpccert=
|
||||
; btcd.rawrpccert=
|
||||
|
||||
|
||||
[Bitcoind]
|
||||
@ -190,7 +194,7 @@ bitcoin.node=btcd
|
||||
; setting is assumed to be localhost with the default port for the current
|
||||
; network.
|
||||
; bitcoind.rpchost=localhost
|
||||
|
||||
|
||||
; Username for RPC connections to bitcoind. By default, lnd will attempt to
|
||||
; automatically obtain the credentials, so this likely won't need to be set
|
||||
; (other than for a remote bitcoind instance).
|
||||
@ -205,7 +209,7 @@ bitcoin.node=btcd
|
||||
; bitcoind. By default, lnd will attempt to automatically obtain this
|
||||
; information, so this likely won't need to be set (other than for a remote
|
||||
; bitcoind instance).
|
||||
; bitcoind.zmqpath=tcp://127.0.0.1:28332
|
||||
; bitcoind.zmqpath=tcp://127.0.0.1:28332
|
||||
|
||||
|
||||
[neutrino]
|
||||
@ -232,7 +236,7 @@ bitcoin.node=btcd
|
||||
litecoin.node=ltcd
|
||||
|
||||
; Use the litecoind back-end
|
||||
; litecoin.node=litecoind
|
||||
; litecoin.node=litecoind
|
||||
|
||||
|
||||
[Ltcd]
|
||||
@ -241,7 +245,7 @@ litecoin.node=ltcd
|
||||
; setting is assumed to be localhost with the default port for the current
|
||||
; network.
|
||||
; ltcd.rpchost=localhost
|
||||
|
||||
|
||||
; Username for RPC connections to ltcd. By default, lnd will attempt to
|
||||
; automatically obtain the credentials, so this likely won't need to be set
|
||||
; (other than for simnet mode).
|
||||
@ -259,7 +263,7 @@ litecoin.node=ltcd
|
||||
; The raw bytes of the daemon's PEM-encoded certificate chain which will be used
|
||||
; to authenticate the RPC connection. This only needs to be set if the ltcd
|
||||
; node is on a remote host.
|
||||
; ltcd.rawrpccert=
|
||||
; ltcd.rawrpccert=
|
||||
|
||||
|
||||
[Litecoind]
|
||||
@ -268,7 +272,7 @@ litecoin.node=ltcd
|
||||
; setting is assumed to be localhost with the default port for the current
|
||||
; network.
|
||||
; litecoind.rpchost=localhost
|
||||
|
||||
|
||||
; Username for RPC connections to litecoind. By default, lnd will attempt to
|
||||
; automatically obtain the credentials, so this likely won't need to be set
|
||||
; (other than for a remote litecoind instance).
|
||||
@ -305,7 +309,7 @@ litecoin.node=ltcd
|
||||
[tor]
|
||||
; The port that Tor's exposed SOCKS5 proxy is listening on. Using Tor allows
|
||||
; outbound-only connections (listening will be disabled) -- NOTE port must be
|
||||
; between 1024 and 65535
|
||||
; between 1024 and 65535
|
||||
; tor.socks=9050
|
||||
|
||||
; The DNS server as IP:PORT that Tor will use for SRV queries - NOTE must have
|
||||
|
Loading…
Reference in New Issue
Block a user