view mod_storage_mongodb/README.markdown @ 4515:2e33eeafe962

mod_muc_markers: Prevent any markers from reaching the archive, even if untracked Original intention was to leave alone things that this module isn't handling. However markers in archives are just problematic without more advanced logic about what is markable and what is not. It also requires a more advanced query in mod_muc_rai to determine the latest markable message instead of the latest archived message. I'd rather keep the "is archivable" and "is markable" definition the same for simplicity. I don't want to introduce yet another set of rules for no reason. No markers in MAM.
author Matthew Wild <mwild1@gmail.com>
date Mon, 22 Mar 2021 15:55:02 +0000
parents 8de50be756e5
children
line wrap: on
line source

---
labels:
- 'Type-Storage'
- 'Stage-Alpha'
summary: MongoDB Storage Module
...

Introduction
============

This is a storage backend that uses MongoDB. Depends on [luamongo
bindings](https://github.com/mwild1/luamongo)

This module is not under active development and has a number of issues
related to limitations in MongoDB. It is not suitable for production
use.

Configuration
=============

Copy the module to the prosody modules/plugins directory.

In Prosody's configuration file, set:

    storage = "mongodb"

MongoDB options are:

  Name         Description
  ------------ -------------------------------------------------------------------
  server       hostname:port
  username     your username for the given database
  password     your password for the given database (either raw or pre-digested)
  is\_digest   whether the password field has been pre-digested

Compatibility
=============

  ------- ---------------------------
  trunk   Untested, but should work
  ------- ---------------------------