mirror of
https://github.com/edouardparis/lntop
synced 2024-11-06 03:20:21 +00:00
9e50120dec
Instead of relying on docker-compose.yml, we use bash to pass configuration to docker directly via commnad-line args. We also use config template and prior each run we evaluate it with current environment. So that settings like LND_GRPC_HOST can be specified prior each run without a need to rebuild. |
||
|---|---|---|
| .. | ||
| lntop | ||
| _settings.sh | ||
| .gitignore | ||
| build.sh | ||
| clean.sh | ||
| inspect.sh | ||
| lntop.sh | ||
| logs.sh | ||
| README.md | ||
Docker
To run lntop from a docker container:
# you should first review ./lntop/home/initial-config-template.toml
# note that paths are relevant to situation inside docker and we run under root
# so $HOME directory is /root
# build the container
./build.sh
# if you have an existing .lntop directory on host machine, you can export it:
# export LNTOP_HOME=~/.lntop
# if you have local lnd node on host machine, point LND_HOME to your actual lnd directory:
export LND_HOME=~/.lnd
# or alternatively if you have remote lnd node, specify paths to auth files explicitly:
# export TLS_CERT_FILE=/path/to/tls.cert
# export ADMIN_MACAROON_FILE=/path/to/admin.macaroon
# export LND_GRPC_HOST=//<remoteip>:10009
# look into _settings.sh for more details on container configuration
# run lntop from the container
./lntop.sh
# lntop data will be mapped to host folder at ./_volumes/lntop-data
# note that you can review/tweak ./_volumes/lntop-data/config-template.toml after first run
# the ./_volumes/lntop-data/config.toml is the effective (generated) config used by lntop run
To see lntop logs, you can tail them in another terminal session via:
./logs.sh -f
To start from scratch:
./clean.sh
./build.sh --no-cache