Mercurial > prosody-modules
comparison mod_reload_modules/README.markdown @ 1803:4d73a1a6ba68
Convert all wiki pages to Markdown
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Fri, 28 Aug 2015 18:03:58 +0200 |
parents | |
children |
comparison
equal
deleted
inserted
replaced
1802:0ab737feada6 | 1803:4d73a1a6ba68 |
---|---|
1 --- | |
2 labels: | |
3 - 'Stage-Stable' | |
4 summary: Automatically reload modules with the config | |
5 ... | |
6 | |
7 Introduction | |
8 ------------ | |
9 | |
10 By default Prosody does not reload modules at runtime unless instructed | |
11 to via one of its admin interfaces. However sometimes you want to easily | |
12 reload a module to apply new settings when the config changes. | |
13 | |
14 mod\_reload\_modules will reload a set list of modules every time | |
15 Prosody reloads its config (e.g. on SIGHUP). | |
16 | |
17 Configuration | |
18 ------------- | |
19 | |
20 Add "reload\_modules" to modules\_enabled. Then the list of modules to | |
21 reload using the 'reload\_modules' option in your config like so: | |
22 | |
23 reload_modules = { "groups", "tls" } | |
24 | |
25 This would reload mod\_groups and mod\_tls whenever the config is | |
26 reloaded. Note that on many systems this will be at least daily, due to | |
27 logrotate. | |
28 | |
29 Compatibility | |
30 ------------- | |
31 | |
32 ----- ------- | |
33 0.9 Works | |
34 ----- ------- |