Mercurial > prosody-modules
view mod_muc_log/README.markdown @ 2809:6d3935226ffb
Backed out changeset 6d72c5172c74
I have no idea why I changed it. Setting it back to 0 allows eg
mod_firewall to work with it.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Mon, 23 Oct 2017 17:22:27 +0200 |
parents | 14f62b971160 |
children | adf84d6a457d |
line wrap: on
line source
--- labels: - 'Stage-Beta' summary: Log chatroom messages to disk ... Introduction ============ This module logs the conversation of chatrooms running on the server to Prosody's data store. To view them you will need a module such as [mod\_muc\_log\_http](mod_muc_log_http.html). Details ======= mod\_muc\_log must be loaded individually for the components that need it. Assuming you have a MUC component already running on conference.example.org then you can add muc\_log to it like so: Component "conference.example.org" "muc" modules_enabled = { "muc_log"; } Logging is not enabled by default. In 0.9+ logging can be enabled per room in the room config form. To enable logging in older versions, or to enable logging by default for all rooms, set muc_log_by_default = true -- Log all rooms by default Compatibility ============= ----- ------- 0.6 Works 0.7 Works 0.8 Works 0.9 Works ----- ------- **Note** that per-room configuration only works in 0.9+.