view mod_muc_log_http/README.markdown @ 4268:871d140d61bb

mod_adhoc_oauth2_client: Fix including final client_id in result form The client_id is composed of the details needed for retrieving the data, making it redundant to include in the data, albeit somewhat convenient sometimes. Decided to remove it anyways, but forgot to change the result.
author Kim Alvefur <zash@zash.se>
date Sun, 22 Nov 2020 17:00:26 +0100
parents 79b9bd84b91c
children
line wrap: on
line source

---
labels:
- 'Stage-Beta'
summary: Provides a web interface to stored chatroom logs
...

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

This module provides a built-in web interface to view chatroom logs
stored by [mod\_muc\_log](mod_muc_log.html).

Installation
============

Just copy the folder muc\_log\_http as it is, into the modules folder of
your Prosody installation.

Configuration Details
=====================

Example configuration:

        Component "conference.example.com" "muc"
        modules_enabled = {
            .....
            "muc_log";
            "muc_log_http";
            .....
        }

        muc_log_http = { -- These are the defaults
            show_join = true;
            show_presences = true;
            show_status = true;
            theme = "prosody";
            url_base = "muc_log";
        }

**show\_join** sets the default for showing joins or leaves.
**show\_status** sets the default for showing status changes.

The web interface would then be reachable at the address:

    http://conference.example.com:5280/muc_log/

TODO
====

-   Log bans correctly
-   Quota \~ per day ?!
-   Testing testing :)