Feature(Config): Dump default config

[a-kenji]

Make it possible to dump a default config to
either stdout or a file.
Possibly with comments explaining the Actions,
related to #247 .

More discussion in #244 ,
especially #224 (comment) .

[a-kenji]

Should be easy to implement once #283 is there.

[matthiasbeyer]

I think this is a good idea, opposing to writing a default configuration automatically on the first run, which I think is a bad idea (since implicit is always worse than explicit).

Having a warning about a missing configuration file and a note on how to create a default config file is IMO a way better user experience than just silently writing a default file to disk and using that.

[a-kenji]

I think this is a good idea, opposing to writing a default configuration automatically on the first run, which I think is a bad idea (since implicit is always worse than explicit).

I agree, this seems like a more sane default.

Having a warning about a missing configuration file and a note on how to create a default config file is IMO a way better user experience than just silently writing a default file to disk and using that.

Maybe have a command that will bootstrap everything for the user? And a different to dump it to stdout?

[matthiasbeyer]

Maybe have a command that will bootstrap everything for the user?

Yep, a nice interactive one probably. Maybe there's even a framework for things like that somewhere, otherwise we could implement a small one (would love to contribute on such a thing)!

And a different to dump it to stdout?

Yep, sounds good.

[a-kenji]

Awesome! I will try to get a different issue to kind of pull all that stuff together soonish.

[imsnif]

@a-kenji - I think this is released already, right?

[a-kenji]

@imsnif - Yes!