view mod_reload_modules/README.markdown @ 4876:0f5f2d4475b9

mod_http_xep227: Add support for import via APIs rather than direct store manipulation In particular this transitions PEP nodes and data to be imported via mod_pep's APIs, fixing issues with importing at runtime while PEP data may already be live in RAM. Next obvious candidate for this approach is rosters, so clients get immediate roster pushes and other special handling (such as emitting subscribes to reach the desired subscription state).
author Matthew Wild <mwild1@gmail.com>
date Tue, 18 Jan 2022 17:01:18 +0000
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
  ----- -------