Software / code / prosody-modules
Comparison
mod_storage_muconference_readonly/README.markdown @ 2222:51596d73157e
mod_storage_muconference_readonly: Initial commit
| author | Emmanuel Gil Peyrot <linkmauve@linkmauve.fr> |
|---|---|
| date | Thu, 30 Jun 2016 05:22:12 +0100 |
| child | 2224:20accfa5b6d6 |
comparison
equal
deleted
inserted
replaced
| 2221:3d80f8dba886 | 2222:51596d73157e |
|---|---|
| 1 --- | |
| 2 labels: | |
| 3 - 'Type-Storage' | |
| 4 - 'Stage-Alpha' | |
| 5 summary: MU-Conference SQL Read-only Storage Module | |
| 6 ... | |
| 7 | |
| 8 Introduction | |
| 9 ============ | |
| 10 | |
| 11 This is a storage backend using MU-Conference’s SQL storage. It depends | |
| 12 on [LuaDBI](https://prosody.im/doc/depends#luadbi) | |
| 13 | |
| 14 This module only works in read-only, and was made to be used by | |
| 15 [mod\_migrate](https://modules.prosody.im/mod_migrate.html) to migrate | |
| 16 from MU-Conference’s SQL storage. | |
| 17 | |
| 18 You may need to convert your 'rooms' and 'rooms\_lists' tables to | |
| 19 utf8mb4 before running that script, in order not to end up with | |
| 20 mojibake. Note that MySQL doesn’t support having more than | |
| 21 191 characters in the jid field in this case, so you may have to change | |
| 22 the table schema as well. | |
| 23 | |
| 24 Configuration | |
| 25 ============= | |
| 26 | |
| 27 Copy the module to the prosody modules/plugins directory. | |
| 28 | |
| 29 In Prosody's configuration file, set: | |
| 30 | |
| 31 storage = "muconference_readonly" | |
| 32 | |
| 33 MUConferenceSQL options are the same as the | |
| 34 [https://prosody.im/doc/modules/mod\_storage\_sql](SQL ones): | |
| 35 | |
| 36 Compatibility | |
| 37 ============= | |
| 38 | |
| 39 ------- --------------------------- | |
| 40 trunk Works | |
| 41 ------- --------------------------- | |
| 42 0.10 Untested, but should work | |
| 43 ------- --------------------------- | |
| 44 0.9 Does not work | |
| 45 ------- --------------------------- |