Mercurial > prosody-modules

view mod_auth_wordpress/README.markdown @ 4515:2e33eeafe962

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
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 4d73a1a6ba68
children
line wrap: on
line source

---
labels:
- 'Stage-Alpha'
- 'Type-Auth'
summary: Wordpress authentication module
...

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

This module allows you to authenticate against an Wordpress database.

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

SQL connection paramaters are identical to those of [SQL
storage](https://prosody.im/doc/modules/mod_storage_sql).

    authentication = "wordpress"
    wordpress_table_prefix = "wp_" -- default table prefix
    sql = { -- See documentation for SQL storage
        driver = "MySQL";
        database = "my_wordpress";
        host = "localhost";
        username = "prosody";
        password = "secretpassword";
    }

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

Prosody 0.8+