#1729 Difficulty discovery what config files are active
Reporter
MattJ
Owner
MattJ
Created
Updated
Stars
★ (1)
Tags
Milestone-0.12
Type-Defect
Priority-Medium
Status-Fixed
MattJ
on
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?
Prosody 0.12.0
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.
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? Prosody 0.12.0 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.
Fixed in 0.12 by https://hg.prosody.im/trunk/rev/dc6263625069
Changes