Mercurial > prosody-modules
view mod_reload_modules/README.markdown @ 5796:93d6e9026c1b
mod_http_oauth2: Do not enforce PKCE on Device and OOB flows
PKCE does not appear to be used with the Device flow. I have found no
mention of any interaction between those standards. Since no data is
delivered via redirects in these cases, PKCE may not serve any purpose.
This is mostly a problem because we reuse the authorization code to
implement the Device and OOB flows.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Fri, 15 Dec 2023 12:10:07 +0100 |
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 ----- -------