Software /
code /
prosody-modules
File
mod_discodot/README.markdown @ 5366:db4c66a1d24b
mod_http_oauth2: Fill in some client metadata defaults
Explicit > Implicit
Maybe we should actually use these for something as well? :)
It's is somewhat an open question of how strictly we should enforce
things in the client metadata given that it is somewhat extensible.
Especially some of these enum fields which have corresponding IANA
registries.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Tue, 25 Apr 2023 18:09:08 +0200 |
parent | 4577:253df0798996 |
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`