We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After thinking more about it, the .lntop/config.toml creation at start up was a mistake which should be fixed in next versions. I think everything needs to be more explicit and reflects the lncli behaviour: https://github.com/lightningnetwork/lnd/blob/master/cmd/lncli/main.go#L263
lntop
.lntop
lntop --rpcserver=<...> --tlscertpath=<...> --macaroonpath=<...>
lntop --conf <...>
The user then creates an alias the .bashrc according to his needs. (tldr: lntop should not create a default config file "polluting" user config)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
After thinking more about it, the .lntop/config.toml creation at start up was a mistake which should be fixed in next versions.
I think everything needs to be more explicit and reflects the lncli behaviour:
https://github.com/lightningnetwork/lnd/blob/master/cmd/lncli/main.go#L263
lntop
: search for config file in.lntop
(for retro compatibility), starts lntop with all default values if no file is foundlntop --rpcserver=<...> --tlscertpath=<...> --macaroonpath=<...>
starts lntop with specified valueslntop --conf <...>
starts with the config valuesThe user then creates an alias the .bashrc according to his needs.
(tldr: lntop should not create a default config file "polluting" user config)
The text was updated successfully, but these errors were encountered: