Mercurial > prosody-modules
view mod_discodot/README.markdown @ 4876:0f5f2d4475b9
mod_http_xep227: Add support for import via APIs rather than direct store manipulation
In particular this transitions PEP nodes and data to be imported via mod_pep's
APIs, fixing issues with importing at runtime while PEP data may already be
live in RAM.
Next obvious candidate for this approach is rosters, so clients get immediate
roster pushes and other special handling (such as emitting subscribes to reach
the desired subscription state).
author | Matthew Wild <mwild1@gmail.com> |
---|---|
date | Tue, 18 Jan 2022 17:01:18 +0000 |
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`