Logs in config only applied to consensus and sync node

[grishy]

Have you read a contributing guide?

• I have read CONTRIBUTING.md
• I have searched the existing issues and didn't find any that were similar
• I have considered creating a pull request with fixes instead of a bug report and want to proceed

Current Behavior

Thanks for project ❤️
I found out that we have a common configuration that includes the log section. However, it seems this section is only read by half of them.

The configuration of the consensus-node and sync-node contains:

• https://github.com/anyproto/any-sync-consensusnode/blob/main/config/config.go#L38
• https://github.com/anyproto/any-sync-node/blob/main/config/config.go#L49

However, if you check the other configurations, they do not include it:

• https://github.com/anyproto/any-sync-filenode/blob/main/config/config.go#L33-L48
• https://github.com/anyproto/any-sync-coordinator/blob/main/config/config.go#L34-L46

Expected Behavior

All nodes were able to read the log configuration.

[fb929]

Hi!
any-sync-* daemons ignore unknown config sections, so I don't think this is a bug, as it doesn't affect the daemon's operation in any way.

[grishy]

@fb929
Yes, I generally agree, it was worth creating it as a feature then, in order to be able to change the log level for each application.
It's just that right now it looks like dockercompose creates configs, some of the fields of which are simply not responsible for anything and changing them does not affect anything.