Mercurial > prosody-modules
view mod_invites/README.md @ 6258:06fbbd45ba75
mod_cloud_notify: Readme: fix links and labels that were removed in the last commit
diff --git a/mod_cloud_notify/README.md b/mod_cloud_notify/README.md
--- a/mod_cloud_notify/README.md
+++ b/mod_cloud_notify/README.md
@@ -1,3 +1,9 @@
+----
+-labels:
+-- 'Stage-Beta'
+-summary: 'XEP-0357: Cloud push notifications'
+----
+
# Introduction
This module enables support for sending "push notifications" to clients
@@ -32,15 +38,15 @@ notification to your device. When your d
it will display it or wake up the app so it can connect to XMPP and
receive any pending messages.
-This protocol is described for developers in \[XEP-0357: Push
-Notifications\].
+This protocol is described for developers in [XEP-0357: Push
+Notifications].
-For this module to work reliably, you must have \[mod_smacks\],
-\[mod_mam\] and \[mod_carbons\] also enabled on your server.
+For this module to work reliably, you must have [mod_smacks],
+[mod_mam] and [mod_carbons] also enabled on your server.
Some clients, notably Siskin and Snikket iOS need some additional
extensions that are not currently defined in a standard XEP. To support
-these clients, see \[mod_cloud_notify_extensions\].
+these clients, see [mod_cloud_notify_extensions].
# Configuration
@@ -58,18 +64,18 @@ these clients, see \[mod_cloud_notify_ex
# Internal design notes
App servers are notified about offline messages, messages stored by
-\[mod_mam\] or messages waiting in the smacks queue. The business rules
+[mod_mam] or messages waiting in the smacks queue. The business rules
outlined
[here](//mail.jabber.org/pipermail/standards/2016-February/030925.html)
are all honored[^2].
-To cooperate with \[mod_smacks\] this module consumes some events:
+To cooperate with [mod_smacks] this module consumes some events:
`smacks-ack-delayed`, `smacks-hibernation-start` and
`smacks-hibernation-end`. These events allow this module to send out
notifications for messages received while the session is hibernated by
-\[mod_smacks\] or even when smacks acknowledgements for messages are
+[mod_smacks] or even when smacks acknowledgements for messages are
delayed by a certain amount of seconds configurable with the
-\[mod_smacks\] setting `smacks_max_ack_delay`.
+[mod_smacks] setting `smacks_max_ack_delay`.
The `smacks_max_ack_delay` setting allows to send out notifications to
clients which aren't already in smacks hibernation state (because the
| author | Menel <menel@snikket.de> |
|---|---|
| date | Fri, 13 Jun 2025 10:44:37 +0200 |
| parents | fe081789f7b5 |
| children | 00735045109d |
line wrap: on
line source
--- labels: - 'Stage-Merged' summary: 'Invite management module for Prosody' ... Introduction ============ ::: {.alert .alert-info} This module has been merged into Prosody as [mod_invites][doc:modules:mod_invites]. Users of Prosody **0.12** and later should not install this version. ::: This module is part of the suite of modules that implement invite-based account registration for Prosody. The other modules are: - [mod_invites_adhoc][doc:modules:mod_invites_adhoc] - [mod_invites_register][doc:modules:mod_invites_register] - [mod_invites_page] - [mod_invites_register_web] - [mod_invites_api] - [mod_register_apps] This module manages the creation and consumption of invite codes for the host(s) it is loaded onto. It currently does not expose any admin/user-facing functionality (though in the future it will probably gain a way to view/manage pending invites). Instead, other modules can use the API from this module to create invite tokens which can be used to e.g. register accounts or create automatic subscription approvals. This module should not be confused with the similarly named mod_invite (note the missing 's'!). That module was a precursor to this one that helped test and prove the concept of invite-based registration, and is now deprecated. # Configuration This module exposes just one option - the length of time that a generated invite should be valid for by default. ``` {.lua} -- Configure the number of seconds a token is valid for (default 7 days) invite_expiry = 86400 * 7 ``` # Invites setup For a fully-featured invite-based setup, the following provides an example configuration: ``` {.lua} -- Specify the external URL format of the invite links VirtualHost "example.com" invites_page = "https://example.com/invite?{invite.token}" http_external_url = "https://example.com/" http_paths = { invites_page = "/invite"; invites_register_web = "/register"; } modules_enabled = { "invites"; "invites_adhoc"; "invites_page"; "invites_register"; "invites_register_web"; "http_libjs"; -- See 'external dependencies' below } ``` Restart Prosody and create a new invite using an ad-hoc command in an XMPP client connected to your admin account, or use the command line: prosodyctl mod_invites generate example.com ## External dependencies The default HTML templates for the web-based modules depend on some CSS and Javascript libraries. They expect these to be available at `https://example.com/share`. An easy way of doing this if you are on Debian 10 (buster) is to enable mod_http_libjs and install the following packages: apt install libjs-bootstrap4 libjs-jquery On other systems you will need to manually put these libraries somewhere on the filesystem that Prosody can read, and serve them using mod_http_libjs with a custom `libjs_path` setting. # Compatibility 0.11 and later.
