#1729 Difficulty discovery what config files are active
What steps will reproduce the problem?
1. Use a config file that has an 'Include' directory (especially a wildcard, which is common)
2. Forget (or don't realise) that there are additional config files being loaded
3. Be puzzled by strange behaviour
What version of the product are you using? On what operating system?
Please provide any additional information below.
It would be ideal if Prosody could inform a user what config files have ultimately been loaded. This could be printed in e.g. 'prosodyctl check config'.
This is not strictly a bug, but a UX issue that has affected multiple people and is easily fixed.