-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
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
Ability to read initial config from environment. #48
Conversation
Thank you for the contribution, please can you specify in the README https://github.com/edouardparis/lntop#config under the config section the three env var introduced in this PR ? |
@edouardparis Yep, done! |
However, if I think about it, it's kinda strange to accept env vars, yet only take them into account if the config file is missing. I think it would make more sense to have them override the values read from config also. What do you think? |
I think the PR is good as it is for the current usage. After thinking more about it, the .lntop/config.toml creation at start up was a mistake which should be fixed in next versions.
The user then creates an alias the .bashrc according to his needs. |
Yes, I agree. Creating a config file with default values seems to do more harm than good. At least, having the env vars (whether to be used as default values in the config file, or to override the config file completely) fixes the problem that we have now, in that one cannot start |
@edouardparis Do you think we can merge this for now? |
Yes sorry, send me a link for a tip |
Thank you again |
Thank you for |
Shall we make an issue for changing the parameters/configuration behavior as discussed above? |
I am creating one, thank you for the reminder |
No description provided.