-
-
Notifications
You must be signed in to change notification settings - Fork 1
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
feat(CLI): add --config
CLI argument
#14
Comments
Maybe we could rely on environment variables use std::env;
let key = "DEAD_MAN_CONFIG";
match env::var(key) {
Ok(val) => { do_something_with_val(val)},
Err(e) => {do_nothing()},
} |
I don't like env vars, I want this to be a CLI argument that you can override. |
ENV vars are good for set and forget stuff. I want to be able to run several DMS with different TOML configs. |
Instead of running multiple instances of DMS the --config arg can be set as a array of paths to watch and iterate over TOML configs... |
with some good byte abstraction, all the TOMLS can be tracked and loaded in memory only retrieving the warning time and the path. Users no more need to fit all the secrets in one toml (if using the way it should be used). Could have several tomls for each secrets |
KISS, let's first implement the simple baby-steps one config? I don't want to overbloat this with |
Right now the config is hardcoded to be created/read in the OS-agnostic config dir.
We need a CLI argument to override it.
Something like:
The text was updated successfully, but these errors were encountered: