Clarify README and REST backend doc
This commit is contained in:
15
README.md
15
README.md
@@ -171,17 +171,26 @@ systemctl start mxisd
|
||||
After following the specific instructions to create a config file from the sample:
|
||||
1. Set the `matrix.domain` value to the domain value used in your Home Server configuration
|
||||
2. Set an absolute location for the signing keys using `key.path`
|
||||
3. Set a location for the default SQLite persistence using `storage.provider.sqlite.database`
|
||||
4. Configure the E-mail invite sender with items starting in `invite.sender.email`
|
||||
3. Configure the E-mail invite sender with items starting in `invite.sender.email`
|
||||
|
||||
In case your IS public domain does not match your Matrix domain, see `server.name` and `server.publicUrl`
|
||||
config items.
|
||||
|
||||
If you want to use the LDAP backend:
|
||||
|
||||
## Backends
|
||||
### LDAP (AD, Samba, LDAP)
|
||||
If you want to use LDAP backend as an Identity store:
|
||||
1. Enable it with `ldap.enabled`
|
||||
2. Configure connection options using items starting in `ldap.connection`
|
||||
3. You may want to valid default values for `ldap.attribute` items
|
||||
|
||||
### SQL (SQLite, PostgreSQL)
|
||||
If you want to connect to use a synapse DB (SQLite or PostgreSQL) as Identity store, follow the example config for `sql` config items.
|
||||
|
||||
### REST (Webapps/websites integration)
|
||||
If you want to use the REST backend as an Identity store:
|
||||
1. Enable it with `rest.enabled`
|
||||
2. Configure options starting with `rest` and see the dedicated documentation in `docs/backends/rest.md`
|
||||
|
||||
# Network Discovery
|
||||
To allow other federated Identity Server to reach yours, the same algorithm used for Homeservers takes place:
|
||||
|
||||
Reference in New Issue
Block a user