Software / code / prosody-modules
File
mod_register_apps/README.md @ 6305:1c62edeb9147
mod_pastebin: Update Readme
diff --git a/mod_pastebin/README.md b/mod_pastebin/README.md
--- a/mod_pastebin/README.md
+++ b/mod_pastebin/README.md
@@ -37,12 +37,14 @@ For example:
Pastes will be available by default at
`http://<your-prosody>:5280/pastebin/` by default.
-In Prosody 0.9 and later this can be changed with [HTTP
-settings](https://prosody.im/doc/http).
+Ports and path can be changed with [HTTP
+settings](https://prosody.im/doc/http), for example like:
-In 0.8 and older this can be changed with `pastebin_ports` (see below),
-or you can forward another external URL from your web server to Prosody,
-use `pastebin_url` to set that URL.
+``` {.lua}
+ http_paths = {
+ pastebin = "/$host-paste";
+ }
+```
# Discovery
@@ -82,27 +84,16 @@ The line and character tresholds are adv
pastebin_line_threshold The maximum number of lines a message may have before it is sent to the pastebin. (default 4 lines)
pastebin_trigger A string of characters (e.g. "!paste ") which if detected at the start of a message, always sends the message to the pastebin, regardless of length. (default: not set)
pastebin_expire_after Number of hours after which to expire (remove) a paste, defaults to 24. Set to 0 to store pastes permanently on disk.
- pastebin_ports List of ports to run the HTTP server on, same format as mod_httpserver's http_ports[^1]
- pastebin_url Base URL to display for pastebin links, must end with / and redirect to Prosody's built-in HTTP server[^2]
# Compatibility
- ------ -------
- trunk Works
+ ------ ---------------------
+ trunk Works as of 25-06-13
+ 13 Works
0.12 Works
- 0.11 Works
- 0.10 Works
- 0.9 Works
- 0.8 Works
- ------ -------
+ ------ ---------------------
# Todo
- Maximum paste length
- Web interface to submit pastes?
-
-[^1]: As of Prosody 0.9, `pastebin_ports` is replaced by `http_ports`,
- see [Prosody HTTP server documentation](https://prosody.im/doc/http)
-
-[^2]: See also
- [http_external_url](https://prosody.im/doc/http#external_url)
| author | Menel <menel@snikket.de> |
|---|---|
| date | Fri, 13 Jun 2025 11:39:58 +0200 |
| parent | 6003:fe081789f7b5 |
line wrap: on
line source
--- labels: - 'Stage-Beta' summary: 'Manage list of compatible client apps' rockspec: build: copy_directories: - assets ... Introduction ============ This module provides a way to configure a list of XMPP client apps recommended by the current server. This list is used by other modules such as mod_invites_page and mod_invites_register_web. It also contains the logos of a number of popular XMPP clients, and serves them over HTTP for other modules to reference when serving web pages. # Configuration | Field | Description | |----------------------|--------------------------------------------------------------------------| | site_apps | A list of apps and their metadata | | site_apps_show | A list of app ids to only show | | site_apps_hide | A list of app ids to never show | An "app id" is the lower case app name, with any spaces replaced by `-`. E.g. "My Chat" would be `"my-chat"`. The module comes with a preconfigured `site_apps` containing popular clients. Patches are welcome to add/update this list as needed! If you want to limit to just displaying a subset of the apps on your server, use the `site_apps_show` option, e.g. `site_apps_show = { "conversations", "siskin-im" }`. To never show specific apps, you can use `site_apps_hide`, e.g. `site_apps_hide = { "pidgin" }`. # App metadata format The configuration option `site_apps` contains the list of apps and their metadata. ``` {.lua} -- Example site_apps config with two clients site_apps = { { name = "Conversations"; text = [[Conversations is a Jabber/XMPP client for Android 4.0+ smartphones that has been optimized to provide a unique mobile experience.]]; image = "assets/logos/conversations.svg"; link = "https://play.google.com/store/apps/details?id=eu.siacs.conversations"; platforms = { "Android" }; supports_preauth_uri = true; magic_link_format = "{app.link!}&referrer={invite.uri}"; download = { buttons = { { image = "https://play.google.com/intl/en_us/badges/static/images/badges/en_badge_web_generic.png"; url = "https://play.google.com/store/apps/details?id=eu.siacs.conversations"; }; }; }; }; { name = "Gajim"; text = [[A fully-featured desktop chat client for Windows and Linux.]]; image = "assets/logos/gajim.svg"; link = "https://gajim.org/"; platforms = { "Windows", "Linux" }; download = { buttons = { { text = "Download Gajim"; url = "https://gajim.org/download/"; target = "_blank"; }; }; }; }; } ``` The fields of each client entry are as follows: | Field | Description | |----------------------|--------------------------------------------------------------------------| | name | The name of the client | | text | Description of the client | | image | URL to a logo for the client, may also be a path in the assets/ directory| | link | URL to the app | | platforms | A list of platforms the app can be installed on | | supports_preauth_uri | `true` if the client supports XEP-0401 preauth URIs | | magic_link_format | A template to generate a magic installation link from an invite | | download | Download instructions and buttons, described below | ## Download metadata The `download` field supports an optional text prompt and one or more buttons. Each button must contain either a `text` or `image` field and must contain a `url` field. It is recommended to set `target = "_blank"` if the link opens a new page, so that the user doesn't lose the invite page. Example download field with instructions and two buttons: ``` {.lua} download = { text = "Some optional instructions about downloading the client..."; buttons = { { text = "Button 1: some text"; url = "https://example.com/"; }; { image = "https://example.com/button2.png"; url = "https://example.com/download/"; }; }; } ```