finallycoffee/matrix-docker-ansible-deploy
finallycoffee/matrix-docker-ansible-deploy
5
1
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update files for matrix-bridge-hookshot: sort logging levels

Browse Source 
Based on docs/configuring-playbook-alertmanager-receiver.md

We can re-sort the levels it if is found out that debug should be placed at the first.

Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
This commit is contained in:
Suguru Hirahara 2025-01-25 18:04:42 +09:00
parent 5c39ef8ca2
commit e8213768a5
No known key found for this signature in database
GPG Key ID: E4F9743DAB4B7B75
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/configuring-playbook-bridge-hookshot.md
View File

@ -153,6 +153,6 @@ As with all other services, you can find the logs in [systemd-journald](https://
The default logging level for this component is `warn`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:
```yaml
# Valid values: debug, info, warn, error
# Valid values: error, warn, info, debug
matrix_hookshot_logging_level: debug
```

2
roles/custom/matrix-bridge-hookshot/defaults/main.yml
View File

@ -183,7 +183,7 @@ matrix_hookshot_provisioning_internal: "/v1"
matrix_hookshot_provisioning_hostname: "{{ matrix_hookshot_public_hostname }}"
matrix_hookshot_provisioning_endpoint: "{{ matrix_hookshot_public_endpoint }}{{ matrix_hookshot_provisioning_internal }}"
# Valid logging levels are: debug, info, warn, error
# Valid values: error, warn, info, debug
matrix_hookshot_logging_level: warn
matrix_hookshot_widgets_enabled: true