Software /
code /
prosody-modules
File
mod_reload_components/README.md @ 6057:cc665f343690
mod_firewall: SUBSCRIBED: Flip subscription check to match documentation
The documentation claims that this condition checks whether the recipient is
subscribed to the sender.
However, it was using the wrong method, and actually checking whether the
sender was subscribed to the recipient.
A quick poll of folk suggested that the documentation's approach is the right
one, so this should fix the code to match the documentation.
This should also fix the bundled anti-spam rules from blocking presence from
JIDs that you subscribe do (but don't have a mutual subscription with).
author | Matthew Wild <mwild1@gmail.com> |
---|---|
date | Fri, 22 Nov 2024 13:50:48 +0000 |
parent | 6003:fe081789f7b5 |
line wrap: on
line source
Introduction ============ This module allows to load/unload external components after they have been added/removed to a configuration file. It is necessary to explicitly initiate a reload on Prosody either via prosodyctl reload or config:reload(). Example 1: -------- If Prosody has started with this configuration file: ``` {.lua} VirtualHost "example.com" authentication = "internal_plain" Component "a.example.com" component_secret = "a" Component "b.example.com" component_secret = "b" ``` And the file has changed manually or dynamically to: ``` {.lua} VirtualHost "example.com" authentication = "internal_plain" Component "a.example.com" component_secret = "a" Component "c.example.com" component_secret = "c" ``` Then, the following actions will occur if this module is loaded: 1. The component c.example.com will be loaded and start bouncing for authentication. 2. The component b.example.com will be unloaded and deactivated. The connection with it will not be closed, but no further actions will be executed on Prosody. Example 2: -------- If Prosody has started with this configuration file: ``` {.lua} VirtualHost "example.com" authentication = "internal_plain" Component "a.example.com" component_secret = "a" ``` And the file has changed manually or dynamically to: ``` {.lua} VirtualHost "example.com" authentication = "internal_plain" Component "a.example.com" component_secret = "a" VirtualHost "newexample.com" authentication = "internal_plain" Component "a.newexample.com" component_secret = "a" ``` Then, the following actions will occur if this module is loaded: 1. The component a.newexample.com will be loaded and start bouncing for authentication. Note that its respective VirtualHost is not loaded. Bad things may happen. Usage ===== Copy the module folder into your Prosody modules directory. Place the module between your enabled modules either into the global or a vhost section. No configuration directives are needed Info ==== - 0.9, works