Mercurial > prosody-modules
view mod_discodot/README.markdown @ 5102:9eed88ac8ee8
mod_s2soutinjection: Use module logging API
_G.log exists but modules should normally use module:log(), or
session.log where applicable.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Fri, 02 Dec 2022 22:05:13 +0100 |
parents | 253df0798996 |
children |
line wrap: on
line source
# Flowcharts! Put this module somewhere Prosody will find it and then run `prosodyctl mod_discodot | dot -Tsvg -o disco-graph.svg` to receive a graph like this[^1]: +------------------------+ +------------------------------------------+ | proxy.external.example | <-- | VirtualHost "example.com" | -+ +------------------------+ +------------------------------------------+ | | | | | v | +------------------------------------------+ | | Component "conference.example.com" "muc" | <+ +------------------------------------------+ Example config for the above: ``` {.lua} VirtualHost "xmpp.example.com" disco_items = { { "conference.example.com"; }; { "proxy.external.example"; }; } Component "conference.example.com" "muc" ``` Note the `disco_items` entry causing duplication since subdomains are implicitly added. [^1]: this was actuall made with `graph-easy`