Skip to content

Re-thinking: Config "watching" #349

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

Closed
Tracked by #376
matthiasbeyer opened this issue Jun 19, 2022 · 1 comment
Closed
Tracked by #376

Re-thinking: Config "watching" #349

matthiasbeyer opened this issue Jun 19, 2022 · 1 comment

Comments

@matthiasbeyer
Copy link
Member

The crate should provide an easy way to implement config "watching" (as in inotify). A user might want to make its application able to react to a changing configuration file, while their app runs.

First of all, this should of course be feature-gated as necessary.
Secondly, I like to believe that this can be implemented in a way that we do not provide the "notify backend" at all, but give the user the opportunity to use interfaces we provide, to build such behavior.

@matthiasbeyer matthiasbeyer changed the title Config "watching" Re-thinking: Config "watching" Jun 19, 2022
@matthiasbeyer
Copy link
Member Author

This plays a bit into what I described here.

The watching functionality is certainly something that is important, but this crate rather focuses on the layering and parsing of configuration, not on the workflow how to handle the configuration.
Such functionality should be implemented outside of the crate, there are other crates that already solve that issue, I guess.

@matthiasbeyer matthiasbeyer mentioned this issue Sep 17, 2022
15 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant