You’re referring to this post:
Appreciate your proposal. I think you’re right and it is a good idea to add it to the server-manager for everyone’s benefit. Your timing is perfect because, as soon as time allows, developers will start working on upgrading ejabberd to a new version.
For the old UI (following MVC design pattern), briefly would be something like:
- adding a config default variable for the setting
- enabling the module on ejabberd.yml through an existing/new default template, based on status of the config default (example using Perl syntax).
- declaring the setting in the Module
- adding setting on the UI View Template
- adding labels on Language file
- adding details on the documentation (1, 2)
Hope the list of steps does not seem daunting, it is easier than it seems (take a look at the code for similar setting).
More info in the developer manual.
For the new Cockpit UI I don’t know, I just can point you to its documentation. I’m sure developers will be able to assist you better and help you along the way if you have any doubts. Don’t hesitate to ask.