Просмотр исходного кода

Adding log level configuration

pull/1912/head
ThellraAK 3 лет назад
Родитель
Сommit
8c4e1ebb18
1 измененных файлов: 9 добавлений и 3 удалений
  1. +9
    -3
      docs/configuring-playbook-bridges.md

+ 9
- 3
docs/configuring-playbook-bridges.md Просмотреть файл

@@ -1,6 +1,3 @@
# Setting up a Mautrix Bridge (optional)


# Setting up a Generic Mautrix Bridge (optional) # Setting up a Generic Mautrix Bridge (optional)


The playbook can install and configure various [mautrix](https://github.com/mautrix) bridges (twitter, facebook, instagram, signal, hangouts, googlechat, etc.), as well as many other (non-mautrix) bridges. The playbook can install and configure various [mautrix](https://github.com/mautrix) bridges (twitter, facebook, instagram, signal, hangouts, googlechat, etc.), as well as many other (non-mautrix) bridges.
@@ -86,6 +83,15 @@ You should generate a strong shared secret with a command like this: pwgen -s 64


This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future. This is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future.


## Controlling the logging level

```yaml
matrix_mautrix_SERVICENAME_logging_level: WARN
```

to `vars.yml` to control the logging level, where you may replace WARN with one of the following to control the verbosity of the logs generated: TRACE, DEBUG, INFO, WARN, ERROR, or FATAL.

If you have issues with a service, and are requesting support, the higher levels of logging will generally be more helpful.




## Usage ## Usage


Загрузка…
Отмена
Сохранить