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
Hi
Every time I want to start a new LNDTOP session, I need to first do export LND_HOME=~/.lnd
And then run it with the longer command, using the full file path.
I wonder if there isn't a way to permanently set the LND_HOME, and also set up a command so I can just type "lntop" in the future.
I was able to do this with bashtop following these instructions (https://bigl.es/tuesday-tooling-on-a-fun-friday-bashtop/), so perhaps it's doable also with lntop - but I don't know, because I didn't try bashtop in a docker.
The text was updated successfully, but these errors were encountered:
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
OK, and then I just do the ./ command to launch it? There's no way to make a quick command line command like "lntop" just launch it?
In any case, fixing the export thing every time would be super helpful, so thank you. I just can't figure out how to get to that config.toml file....? when you say "on the volume" I guess you mean in the docker?
Hi
Every time I want to start a new LNDTOP session, I need to first do
export LND_HOME=~/.lnd
And then run it with the longer command, using the full file path.
I wonder if there isn't a way to permanently set the LND_HOME, and also set up a command so I can just type "lntop" in the future.
I was able to do this with bashtop following these instructions (https://bigl.es/tuesday-tooling-on-a-fun-friday-bashtop/), so perhaps it's doable also with lntop - but I don't know, because I didn't try bashtop in a docker.
The text was updated successfully, but these errors were encountered: