stabilize config loading

[dswij]

related to #3

Currently, dura will read config from config file directly each time it needs to. Only loading config file when dura starts/reloaded is a nicer experience when a user is trying to change the config file (and suits well if dura planned to be a daemon)

[JakeStanger]

I might be missing something stupid/obvious but I'm unsure about this myself. It would be best practice to only load the config on startup and then keep it in memory, but this adds a lot of complexity.

Changes from dura watch or dura unwatch would need to be communicated to the daemon somehow, or you now need to systemctl restart dura (or whatever you're using) every time you watch/unwatch any dir or change how a dir is watched.

The only "downside" with the current implementation in my own eyes is the fact it's making unnecessary disk reads, but they're tiny. We've effectively got hot config reloading regardless of how dura runs with a very simple implementation, and that's pretty darn cool.

[tkellogg]

@dswij what is wrong with the user experience as it currently is?