Mercurial > prosody-modules
view mod_storage_multi/README.md @ 6085:c0cb43817b7c
mod_compliance_latest: using module:log_status
diff --git a/mod_compliance_latest/mod_compliance_latest.lua b/mod_compliance_latest/mod_compliance_latest.lua
--- a/mod_compliance_latest/mod_compliance_latest.lua
+++ b/mod_compliance_latest/mod_compliance_latest.lua
@@ -1,6 +1,6 @@
local success, err = pcall(function() module:depends("compliance_2023") end)
if not success then
- module:log("error", "Error, can't load module: mod_compliance_2023. Is this module downloaded in a folder readable by prosody?")
- return 1, "Error: Couldn't load dependency mod_compliance_2023."
+module:log_status( "error", "Error, can't load module: mod_compliance_2023. Is this module downloaded into a folder readable by prosody?" )
+return false
end
| author | Menel <menel@snikket.de> |
|---|---|
| date | Mon, 23 Dec 2024 14:09:56 +0100 |
| parents | fe081789f7b5 |
| children |
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"`.
