Software /
code /
prosody-modules
File
mod_storage_multi/README.markdown @ 4326:f6fdefc5c6ac
mod_roster_command: Fix subscription when the "user JID" is a bare domain.
Do not attempt to update the roster when the user is bare domain (e.g. a
component), since they don't have rosters and the attempt results in an error:
$ prosodyctl mod_roster_command subscribe proxy.example.com contact@example.com
xxxxxxxxxxFailed to execute command: Error: /usr/lib/prosody/core/rostermanager.lua:104: attempt to concatenate local 'username' (a nil value)
stack traceback:
/usr/lib/prosody/core/rostermanager.lua:104: in function 'load_roster'
/usr/lib/prosody/core/rostermanager.lua:305: in function 'set_contact_pending_out'
mod_roster_command.lua:44: in function 'subscribe'
author | Boris Grozev <boris@jitsi.org> |
---|---|
date | Tue, 05 Jan 2021 13:15:00 -0600 |
parent | 1887:a7fdab9c14e2 |
line wrap: on
line source
--- summary: Multi-backend storage module (WIP) labels: - NeedDocs - Stage-Alpha ... Introduction ============ This module attemtps to provide a storage driver that is really multiple storage drivers. This could be used for storage error tolerance or caching of data in a faster storage driver. Configuration ============= An example: ``` {.lua} storage = "multi" storage_multi_policy = "all" storage_multi = { "memory", "internal", "sql" } ``` Here data would be first read from or written to [mod\_storage\_memory], then internal storage, then SQL storage. For reads, the first successful read will be used. For writes, it depends on the `storage_multi_policy` option. If set to `"all"`, then all storage backends must report success for the write to be considered successful. Other options are `"one"` and `"majority"`.