Mercurial > prosody-modules

view mod_storage_muc_log/README.markdown @ 4515:2e33eeafe962

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
mod_muc_markers: Prevent any markers from reaching the archive, even if untracked Original intention was to leave alone things that this module isn't handling. However markers in archives are just problematic without more advanced logic about what is markable and what is not. It also requires a more advanced query in mod_muc_rai to determine the latest markable message instead of the latest archived message. I'd rather keep the "is archivable" and "is markable" definition the same for simplicity. I don't want to introduce yet another set of rules for no reason. No markers in MAM.
author Matthew Wild <mwild1@gmail.com>
date Mon, 22 Mar 2021 15:55:02 +0000
parents 058844edcaaf
children
line wrap: on
line source

---
labels:
- 'Stage-Alpha'
- ArchiveStorage
summary: 'Storage module using mod\_muc\_log data with new stanza archive API'
---

Introduction
============

[mod\_muc\_log] provided logging of chatrooms running on the server to
Prosody's data store. This module gives access to this data using the
0.10+ stanza archive API, allowing legacy log data to be used with
[mod\_mam\_muc] and [mod\_http\_muc\_log].

Details
=======

Replace [mod\_muc\_log] and [mod\_muc\_log\_http] in your config
with

``` {.lua}
Component "conference.example.org" "muc"
modules_enabled = {
  -- "muc_log"; -- functionality replaced by mod_mam_muc + mod_storage_muc_log
    "mam_muc"; -- Does logging to storage backend configured below

    -- "muc_log_http"; -- Replaced by the mod_http_muc_log
    "http_muc_log";
}
storage = {
  muc_log = "muc_log";
}
```

Compatibility
=============

  version   status
  --------- ---------------
  0.9       unknown
  0.10      works
  0.11      does not work