Mercurial > prosody-modules
view mod_reload_modules/README.markdown @ 4989:b74d592df9e2
mod_http_muc_log: Remove dead code
This might be something left over since a different variant where the
loop went like `for n = i-1, i-100, -1 do ... end` i.e. it went trough a
fixed number of items instead of all the page until the current message.
Then it would have needed something to stop going over the end, but
since the checks are simple it shouldn't be much of a problem looping
over even a very busy day.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Tue, 16 Aug 2022 01:27:59 +0200 |
parents | 4d73a1a6ba68 |
children |
line wrap: on
line source
--- labels: - 'Stage-Stable' summary: Automatically reload modules with the config ... Introduction ------------ By default Prosody does not reload modules at runtime unless instructed to via one of its admin interfaces. However sometimes you want to easily reload a module to apply new settings when the config changes. mod\_reload\_modules will reload a set list of modules every time Prosody reloads its config (e.g. on SIGHUP). Configuration ------------- Add "reload\_modules" to modules\_enabled. Then the list of modules to reload using the 'reload\_modules' option in your config like so: reload_modules = { "groups", "tls" } This would reload mod\_groups and mod\_tls whenever the config is reloaded. Note that on many systems this will be at least daily, due to logrotate. Compatibility ------------- ----- ------- 0.9 Works ----- -------