mod_compliance_latest: New module that depends on and therefore loads the latest compliance tester mod. diff --git a/mod_compliance_latest/README.md b/mod_compliance_latest/README.md new file mode 100644 --- /dev/null +++ b/mod_compliance_latest/README.md @@ -0,0 +1,25 @@ +--- +summary: XMPP Compliance Suites self-test +labels: +- Stage-Beta +rockspec: + dependencies: + - mod_compliance_2023 +... + +# Introduction + +This module will always require and load to the lastest compliance tester we have in the community modules. +Currently this is [mod_compliance_2023]. + +# Configuration + +Just load this module as any other module and it will automatically install [mod_compliance_2023] if you use the Prosody plugin installer. +See the linked module for further details. + +# Compatibility + + Prosody-Version Status + --------------- ---------------------- + trunk Works as of 2024-12-22 + 0.12 Works diff --git a/mod_compliance_latest/mod_compliance_latest.lua b/mod_compliance_latest/mod_compliance_latest.lua new file mode 100644 --- /dev/null +++ b/mod_compliance_latest/mod_compliance_latest.lua @@ -0,0 +1,1 @@ +module:depends("compliance_2023");

---
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
  ----- -------