File

mod_storage_muc_log/README.md @ 6199:fe8222112cf4

mod_conversejs: Serve base app at / This makes things slightly less awkward for the browser to figure out which URLs belong to a PWA. The app's "start URL" was previously without the '/' and therefore was not considered within the scope of the PWA. Now the canonical app URL will always have a '/'. Prosody/mod_http should take care of redirecting existing links without the trailing / to the new URL. If you have an installation at https://prosody/conversejs then it is now at https://prosody/conversejs/ (the first URL will now redirect to the second URL if you use it). The alternative would be to make the PWA scope include the parent, i.e. the whole of https://prosody/ in this case. This might get messy if other PWAs are provided by the same site or Prosody installation, however.
author Matthew Wild <mwild1@gmail.com>
date Tue, 11 Feb 2025 13:18:38 +0000
parent 6003:fe081789f7b5
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