Mercurial > prosody-modules

view mod_storage_muc_log/README.markdown @ 5461:06640647d193

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
mod_http_oauth2: Fix use of arbitrary ports in loopback redirect URIs Per draft-ietf-oauth-v2-1-08#section-8.4.2 > The authorization server MUST allow any port to be specified at the > time of the request for loopback IP redirect URIs, to accommodate > clients that obtain an available ephemeral port from the operating > system at the time of the request. Uncertain if it should normalize the host part, but it also seems harmless to treat IPv6 and IPv4 the same here. One thing is that "localhost" is NOT RECOMMENDED because it can sometimes be pointed to non-loopback interfaces via DNS or hosts file.
author Kim Alvefur <zash@zash.se>
date Wed, 17 May 2023 13:51:30 +0200
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